From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, Eli Zaretskii <eliz@is.elta.co.il>
Cc: ac131313@ges.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfc/rfa:doco] Use @sc{gdb}?
Date: Thu, 26 Sep 2002 12:05:00 -0000 [thread overview]
Message-ID: <1020926190513.ZM19271@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "Re: [rfc/rfa:doco] Use @sc{gdb}?" (Sep 26, 1:40pm)
On Sep 26, 1:40pm, Andrew Cagney wrote:
> >> Date: Fri, 23 Aug 2002 18:33:51 -0400
> >> From: Andrew Cagney <ac131313@ges.redhat.com>
> >>
> >> I got annoyed at all the GDB's in the formatted manual being really
> >> large so tried changing them to @sc{gdb}. It fixed that problem but I'm
> >> not sure that I like the final result :-) (You'll need to build
> >> gdb.pdf, gdb ps or gdb.dvi).
> >>
> >> Is there a style guide thing on this one? Eli?
> >
> >
> > There are no strict rules on this one, AFAIK. If the results of
> > @sc{gdb} look nice to people, let's do it; if not, let's not.
> >
> > Personally, I like the results of @sc in such cases.
>
> So, decision time. Trunk and 5.3 branch?
Having just been through this with GNU vs @sc{gnu}, I think it makes
sense to do it for GDB.
Andrew, what bothered you about the result? (You said that you weren't
sure that you liked the final result.)
Kevin
next prev parent reply other threads:[~2002-09-26 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 15:42 Andrew Cagney
2002-08-24 2:31 ` Eli Zaretskii
2002-09-26 10:40 ` Andrew Cagney
2002-09-26 12:05 ` Kevin Buettner [this message]
2002-09-26 12:52 ` Andrew Cagney
2002-09-27 9:40 ` Eli Zaretskii
2002-09-27 10:55 ` Andrew Cagney
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=1020926190513.ZM19271@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=ac131313@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.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