Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: RFA: fix node name (revised patch)
Date: Sat, 25 Oct 2003 04:00:00 -0000	[thread overview]
Message-ID: <vt24qxyq85w.fsf@zenia.home> (raw)
In-Reply-To: <vt2he1yqbsl.fsf@zenia.home>


Here's a revision of the patch that fixes the menu in the parent node,
too.  (Oops.)

I was trying to figure out why this hasn't bothered anyone yet --- the
node name with the single quotes has been in there for months --- and
I realized that it is because I'm using an older version of
texinfo.tex (circa 1999).  So, Eli, if your response to this patch is
"You should update your texinfo.tex", then that's perfectly fine with
me.

2003-10-24  Jim Blandy  <jimb@redhat.com>

	* gdb.texinfo (The F request packet, The F reply packet): Renamed
	from "The `F' request packet" and "The `F' reply packet", to make
	texi2dvi happy.
	(File-I/O remote protocol extension): Update menu entries, too.

Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.183
diff -c -r1.183 gdb.texinfo
*** gdb/doc/gdb.texinfo	23 Oct 2003 00:11:59 -0000	1.183
--- gdb/doc/gdb.texinfo	25 Oct 2003 03:56:08 -0000
***************
*** 20370,20377 ****
  @menu
  * File-I/O Overview::
  * Protocol basics::
! * The `F' request packet::
! * The `F' reply packet::
  * Memory transfer::
  * The Ctrl-C message::
  * Console I/O::
--- 20370,20377 ----
  @menu
  * File-I/O Overview::
  * Protocol basics::
! * The F request packet::
! * The F reply packet::
  * Memory transfer::
  * The Ctrl-C message::
  * Console I/O::
***************
*** 20498,20504 ****
  After having done the needed type and value coercion, the target continues
  the latest continue or step action.
  
! @node The `F' request packet
  @subsection The @code{F} request packet
  @cindex file-i/o request packet
  @cindex @code{F} request packet
--- 20498,20504 ----
  After having done the needed type and value coercion, the target continues
  the latest continue or step action.
  
! @node The F request packet
  @subsection The @code{F} request packet
  @cindex file-i/o request packet
  @cindex @code{F} request packet
***************
*** 20525,20531 ****
  from its predecessor by a comma.  All values are transmitted in ASCII
  string representation, pointer/length pairs separated by a slash.
  
! @node The `F' reply packet
  @subsection The @code{F} reply packet
  @cindex file-i/o reply packet
  @cindex @code{F} reply packet
--- 20525,20531 ----
  from its predecessor by a comma.  All values are transmitted in ASCII
  string representation, pointer/length pairs separated by a slash.
  
! @node The F reply packet
  @subsection The @code{F} reply packet
  @cindex file-i/o reply packet
  @cindex @code{F} reply packet


  reply	other threads:[~2003-10-25  4:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-25  2:41 RFA: fix node name Jim Blandy
2003-10-25  4:00 ` Jim Blandy [this message]
2003-10-25 13:02   ` RFA: fix node name (revised patch) Eli Zaretskii
2003-10-25 13:03   ` Eli Zaretskii
2003-10-28 22:00     ` Jim Blandy
2003-10-29  6:18       ` Eli Zaretskii
2003-10-25 13:00 ` RFA: fix node name Eli Zaretskii

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=vt24qxyq85w.fsf@zenia.home \
    --to=jimb@redhat.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