From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: [kbd] [ANNOUNCE] upcoming release
Date: Mon, 26 Dec 2016 17:29:56 +0100 [thread overview]
Message-ID: <20161226162956.GB22155@comp-core-i7-2640m-0182e6.fortress> (raw)
Greetings!
Since accumulated a lot of important changes I plan to soon release a new
release. The release will be January 8, 2017.
Changelog:
Alexey Gladkov (9):
Add bar to turkish keymap
Update pancyrillic
loadkeys: require a console device only to load keymap
Remove duplicate rules from makefile
Fix tests
Rename README to README.md
Include config.h first
Check the return code of getfd
Reformat source code in the single style
Felix Janda (2):
ksyms: Fix out of bounds memory read in codetoksym
tests: Fix typo in dumpkeys-fulltable
Marko Myllynen (3):
eurlatgr: add Adobe Latin 2 / 3 support
eurlatgr: add support for U+202F
Update README.eurlatgr to match the updated list
Mike Frysinger (1):
add configure flag to disable tests
Oleg Bulatov (17):
Fix loop limits for unicode case
Fill empty fields in syms.*.h
Extend iso_8859_9_syms
Simplify charset related code
Remove autogenerated files
Fix handling of K_NOSUCHMAP
Fix unicode and diacs dump
Fix strings dump
Generate some syms.*.h from consoletrans files
Fix reduce/reduce conflict
Use unicode name for cyrillic letter dzhe (was dze)
Use unicode name for letter ghe with upturn
Use keysyms in diacs dump
Respect charset in non-unicode dumpkeys
Fix reading KT_LETTER from hex
Generate cp1250 from consoletrans file
Add .travis.yml
Perry Thompson (1):
Add carpalx keymap
Thomas Petazzoni (1):
Link against libintl when needed
Vitezslav Crhonek (1):
Improve consistency of man pages and usage messages.
Xose Vazquez Perez (1):
kbd: install getkeycodes/setkecodes binaries on SPARC
--
Rgrds, legion
reply other threads:[~2016-12-26 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161226162956.GB22155@comp-core-i7-2640m-0182e6.fortress \
--to=gladkov.alexey@gmail.com \
--cc=kbd@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).