public inbox for kbd@lists.linux.dev
 help / color / mirror / Atom feed
From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Cc: matthew@linuxfromscratch.org
Subject: Re: [kbd] kbd-1.15 lat1-16 font issues with groff-1.20.1
Date: Sat, 07 Mar 2009 02:55:55 +0300	[thread overview]
Message-ID: <49B1B80B.3090301@gmail.com> (raw)
In-Reply-To: <e91be5679e9d5a90650faeb4107ad06d@quantum.linuxfromscratch.org>

On 28.02.2009 21:09, Matthew Burgess wrote:
> I've also added mappings for the 2 'quote' type characters that GCC
> outputs in some of its warnings.

Applied, thanks!

-- 
Rgrds, legion



  reply	other threads:[~2009-03-06 23:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49A78A87.3000900@gmail.com>
2009-02-28 18:09 ` [kbd] kbd-1.15 lat1-16 font issues with groff-1.20.1 Matthew Burgess
2009-03-06 23:55   ` Alexey Gladkov [this message]
     [not found] <200902121900.03293.edimitro@tee.gr>
2009-02-16 23:50 ` Matthew Burgess
2009-02-18 21:22   ` Alexey Gladkov
     [not found] <d0239282eabaf6acc990ed5b73297d1d@quantum.linuxfromscratch.org>
2009-02-11 22:17 ` Alexey Gladkov
2009-02-12 16:12   ` Lefteris Dimitroulakis

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=49B1B80B.3090301@gmail.com \
    --to=gladkov.alexey@gmail.com \
    --cc=kbd@lists.altlinux.org \
    --cc=matthew@linuxfromscratch.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