From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: pause after sending S-records to ROM68K monitor
Date: Thu, 09 Aug 2001 09:15:00 -0000 [thread overview]
Message-ID: <np3d71xl83.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010809091643.7420I-100000@is>
Eli Zaretskii <eliz@is.elta.co.il> writes:
> The patch for the manual is approved, but please change "at" into "in"
> in this:
>
> > ! the description of @code{set baud} at @ref{Protocol,, Communication
> > ! Protocol}.
>
> (``at section "Communication Protocol"'', which is what TeX produces
> from this, sounds incorrect English).
Will do, thanks.
next prev parent reply other threads:[~2001-08-09 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 17:54 Jim Blandy
2001-08-08 23:16 ` Eli Zaretskii
2001-08-09 9:15 ` Jim Blandy [this message]
2001-08-09 10:39 ` Andrew Cagney
2001-08-10 14:41 ` Jim Blandy
2001-08-10 17:13 ` Andrew Cagney
2001-08-10 21:02 ` Jim Blandy
2001-08-10 21:14 ` Andrew Cagney
2001-08-10 10:45 ` Frank Ch. Eigler
2001-08-10 14:44 ` Jim Blandy
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=np3d71xl83.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.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