From: Alexey Gladkov <legion@altlinux.ru>
To: Bernardo Innocenti <bernie@codewiz.org>
Cc: Dennis Gilmore <dennis@ausil.us>,
"Andries E. Brouwer" <Andries.Brouwer@cwi.nl>,
vcrhonek@fedoraproject.org,
Walter Bender <walter.bender@gmail.com>,
kbd <kbd@lists.altlinux.org>
Subject: Re: [kbd] OLPC specific keymaps
Date: Sat, 12 Jan 2008 02:50:43 +0300 [thread overview]
Message-ID: <478800D3.4090705@altlinux.ru> (raw)
In-Reply-To: <478617BB.70202@codewiz.org>
Bernardo Innocenti wrote:
> Alexey Gladkov wrote:
>
>> Please, send me example too. :)
>
> Attached. If they seem ok, please feel free to add them to your
> upstream package in i386/olpc/.
I haven't OLPC hardware to test these keymaps, so I add them as is.
http://git.altlinux.org/people/legion/packages/kbd.git?p=kbd.git;a=shortlog;h=1.14wip
--
Rgrds, legion
prev parent reply other threads:[~2008-01-11 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47854CE6.1040501@codewiz.org>
[not found] ` <20080110002539.GA32184@mette>
2008-01-10 7:35 ` [kbd] OLPC specific keymaps Alexey Gladkov
2008-01-10 13:03 ` Bernardo Innocenti
2008-01-11 23:50 ` Alexey Gladkov [this message]
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=478800D3.4090705@altlinux.ru \
--to=legion@altlinux.ru \
--cc=Andries.Brouwer@cwi.nl \
--cc=bernie@codewiz.org \
--cc=dennis@ausil.us \
--cc=kbd@lists.altlinux.org \
--cc=vcrhonek@fedoraproject.org \
--cc=walter.bender@gmail.com \
/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