All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Dustin Kirkland <kirkland@ubuntu.com>
Cc: Seth Forshee <seth.forshee@canonical.com>,
	Michael Schutte <michi@debian.org>,
	Linux console tools development discussion
	<kbd@lists.altlinux.org>
Subject: Re: [kbd] Feature Request: add the setvtrgb utility
Date: Mon, 04 Apr 2011 18:49:27 +0400	[thread overview]
Message-ID: <4D99DA77.8060408@gmail.com> (raw)
In-Reply-To: <BANLkTikH3OJJK89aJ_82L23mSq+2L75vjA@mail.gmail.com>

04.04.2011 18:24, Dustin Kirkland wrote:
>> Historically, all authors are listed in the COPYING. Of course, I have
>> listed you among the authors. Look at my commit.
>>
>> Is it ok for you ?
> 
> Looks good!  Thanks so much for being a great upstream, reviewing,
> rewriting, and accepting this upstream in such a timely manner ;-)
> 
> Do you have any roadmap or schedule for the next kbd release that
> would include this utility?

I'd really like to solve the problem of duplication of names of files
in directories (it's the goal for 1.6). I am currently working on
optimizing loadkeys. If you need this utility I can do an 1.15.3
release. But I need help to test the refs/heads/loadkeys branch.

-- 
Rgrds, legion



  parent reply	other threads:[~2011-04-04 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinA-dur8+mqEpMLHorD-OOPCJZiDTk3fO+X68Op@mail.gmail.com>
2011-03-28 20:29 ` [kbd] Feature Request: add the setvtrgb utility Dustin Kirkland
2011-04-01 23:39   ` Alexey Gladkov
     [not found]     ` <BANLkTinW4DQpVTWNqHv2StnJDEnvXPAbBw@mail.gmail.com>
2011-04-04 14:12       ` Alexey Gladkov
     [not found]         ` <BANLkTikH3OJJK89aJ_82L23mSq+2L75vjA@mail.gmail.com>
2011-04-04 14:49           ` Alexey Gladkov [this message]
2011-04-04 15:02             ` Dustin Kirkland
2011-04-04 16:38           ` Michael Schutte

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=4D99DA77.8060408@gmail.com \
    --to=gladkov.alexey@gmail.com \
    --cc=kbd@lists.altlinux.org \
    --cc=kirkland@ubuntu.com \
    --cc=michi@debian.org \
    --cc=seth.forshee@canonical.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.