From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: [kbd] [ANNOUNCE] kbd-2.0.3 (stable)
Date: Tue, 14 Jul 2015 01:46:47 +0300 [thread overview]
Message-ID: <55A43FD7.2060709@gmail.com> (raw)
kbd 2.0.3 Release Notes
==========================
The kbd-2.0.3 is available at
ftp://ftp.altlinux.org/pub/people/legion/kbd/
ftp://ftp.kernel.org/pub/linux/utils/kbd/
Git repository
--------------
git://git.altlinux.org/people/legion/packages/kbd.git
git://git.kernel.org/pub/scm/linux/kernel/git/legion/kbd.git
https://github.com/legionus/kbd.git
Feedback and bug reports, as always, are welcomed.
Changelog
---------
Alexey Gladkov (15):
Add sun fonts
fr-bepo.map: Add missing keycode definitions
dvorak-es.map: Fix include
loadkeys: Add option to search and parse keymap
Revert part of 1.12-9-gc6af796
Replace error() by kbd_error()
Fix kbd_error
Reduce perror usage
Update README
Add Latin American Dvorak keymap
Close descriptor after use
Fix memory leak
Update pot
po: Update translations (from translationproject.org)
v2.0.3
Dmitry V. Levin (2):
vlock: move some code around
vlock: handle disappearing ttys gracefully
Felix Janda (10):
src/kbdrate: iconv from iso-8859-2 to utf8
libkeymap: include <sys/types.h> for u_short
kbdrate.c, openvt.c: include <fcntl.h> for open()
openvt.c: include <limits.h> for NAME_MAX
<sys/io.h> is already enough to get ioperm()
setvtrgb: Don't gratuitously use malloc
setvtrgb: simplify loop
setvtrgb: inline set_colormap
kbd_error(0,...) -> kbd_warning(), so that kbd_error can be reverted to previous version
Remove dependency on <linux/types.h> by writing out u_char and u_short
Marko Myllynen (2):
README.eurlatgr: describe differences with other often used fonts
Add README.eurlatgr.mappings
Merlin Dou (1):
Add dvorak-programmer keymap
Vinícius dos Santos Oliveira (1):
br-abnt2: added support for AltGr + Q and AltGr + W key combinations.
Álvar Ibeas (1):
keymaps.5: Fix markup
--
Rgrds, legion
reply other threads:[~2015-07-13 22:46 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=55A43FD7.2060709@gmail.com \
--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