From: Andrew Cagney <ac131313@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] gdb.texinfo: Use GNU/Linux instead of Linux
Date: Thu, 26 Sep 2002 10:40:00 -0000 [thread overview]
Message-ID: <3D934682.1060708@redhat.com> (raw)
In-Reply-To: <1020925225930.ZM15134@localhost.localdomain>
> On Sep 21, 11:35am, Eli Zaretskii wrote:
>
>
>> I think in gdb.texinfo the convention is to use @sc{gnu} throughout.
>
>
> Okay.
>
>
>> As for GNU/Linux, I'd suggest first to see whether @sc{gnu}/Linux
>> looks fine in print, and then decide. Kevin, could you please TeX the
>> manual and see whether the result is plausible?
>
>
> Prior to this, I'd generated html and could see no difference. This
> time I generated a pdf file. ``@sc{gnu}'' generates slightly smaller
> characters and looks quite nice (IMO).
>
>
>> Otherwise, okay. Thanks.
>
>
> Committed.
Kevin, can you please pull this into the 5.3 branch?
Andrew
next prev parent reply other threads:[~2002-09-26 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 17:50 Kevin Buettner
2002-09-21 1:35 ` Eli Zaretskii
2002-09-25 15:59 ` Kevin Buettner
2002-09-26 10:40 ` Andrew Cagney [this message]
2002-09-26 17:23 ` Kevin Buettner
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=3D934682.1060708@redhat.com \
--to=ac131313@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.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