From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: ["patch"/rfa/doc] Doco branch commit policy
Date: Thu, 07 Mar 2002 12:06:00 -0000 [thread overview]
Message-ID: <7263-Thu07Mar2002220415+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <3C86CD15.6070401@cygnus.com> (message from Andrew Cagney on Wed, 06 Mar 2002 21:14:45 -0500)
> Date: Wed, 06 Mar 2002 21:14:45 -0500
> From: Andrew Cagney <ac131313@cygnus.com>
>
> @item
> the further a change is from the core of @value{GDBN} the less likely
> the change will worry anyone (i.e. target specific code).
You need a "@:" after "i.e.", otherwise TeX will typeset it as a
sentence end.
> This means that changes such as adding a new new architectures or
Two "new"s in a row.
prev parent reply other threads:[~2002-03-07 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 18:14 Andrew Cagney
2002-03-07 12:06 ` Eli Zaretskii [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=7263-Thu07Mar2002220415+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--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