Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa:doco] switch <- and -> in remote examples
Date: Fri, 23 Aug 2002 13:32:00 -0000	[thread overview]
Message-ID: <3D669B41.50809@ges.redhat.com> (raw)
In-Reply-To: <20020823202405.GA30960@nevyn.them.org>

[-- Attachment #1: Type: text/plain, Size: 385 bytes --]

> On Fri, Aug 23, 2002 at 04:14:25PM -0400, Andrew Cagney wrote:
> 
>> Hello,
>> 
>> This patch just switches the use of <- and -> in the remote protocol 
>> example.  I think it reads better vis:
>> 
>> 	-> Z?
>> 	<- OK
>> 
>> (well at least for a left to right reader :-/).
> 
> 
> (No patch, but) I agree.  -> should be what the client is sending,
> since it's a client manual.
> 


[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 2662 bytes --]

2002-08-23  Andrew Cagney  <ac131313@redhat.com>
 
 	* gdb.texinfo (Examples): Use ``->'' for a packet send and ``<-''
 	for a packet receive.
 
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.114
diff -p -r1.114 gdb.texinfo
*** doc/gdb.texinfo	19 Aug 2002 22:09:03 -0000	1.114
--- doc/gdb.texinfo	23 Aug 2002 20:06:34 -0000
*************** protocol---for example, if there is only
*** 14248,14254 ****
  machine, you might want your program to do something special if it
  recognizes a packet meant for @value{GDBN}.
  
! In the examples below, @samp{<-} and @samp{->} are used to indicate
  transmitted and received data respectfully.
  
  @cindex protocol, @value{GDBN} remote serial
--- 14248,14254 ----
  machine, you might want your program to do something special if it
  recognizes a packet meant for @value{GDBN}.
  
! In the examples below, @samp{->} and @samp{<-} are used to indicate
  transmitted and received data respectfully.
  
  @cindex protocol, @value{GDBN} remote serial
*************** the package was received correctly) or @
*** 14290,14297 ****
  retransmission):
  
  @smallexample
! <- @code{$}@var{packet-data}@code{#}@var{checksum}
! -> @code{+}
  @end smallexample
  @noindent
  
--- 14290,14297 ----
  retransmission):
  
  @smallexample
! -> @code{$}@var{packet-data}@code{#}@var{checksum}
! <- @code{+}
  @end smallexample
  @noindent
  
*************** Example sequence of a target being re-st
*** 15082,15110 ****
  does not get any direct output:
  
  @smallexample
! <- @code{R00}
! -> @code{+}
  @emph{target restarts}
! <- @code{?}
! -> @code{+}
! -> @code{T001:1234123412341234}
  <- @code{+}
  @end smallexample
  
  Example sequence of a target being stepped by a single instruction:
  
  @smallexample
! <- @code{G1445@dots{}}
! -> @code{+}
! <- @code{s}
! -> @code{+}
! @emph{time passes}
! -> @code{T001:1234123412341234}
  <- @code{+}
! <- @code{g}
  -> @code{+}
! -> @code{1455@dots{}}
  <- @code{+}
  @end smallexample
  
  @include gpl.texi
--- 15082,15110 ----
  does not get any direct output:
  
  @smallexample
! -> @code{R00}
! <- @code{+}
  @emph{target restarts}
! -> @code{?}
  <- @code{+}
+ <- @code{T001:1234123412341234}
+ -> @code{+}
  @end smallexample
  
  Example sequence of a target being stepped by a single instruction:
  
  @smallexample
! -> @code{G1445@dots{}}
  <- @code{+}
! -> @code{s}
! <- @code{+}
! @emph{time passes}
! <- @code{T001:1234123412341234}
  -> @code{+}
! -> @code{g}
  <- @code{+}
+ <- @code{1455@dots{}}
+ -> @code{+}
  @end smallexample
  
  @include gpl.texi

  reply	other threads:[~2002-08-23 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-23 13:23 Andrew Cagney
2002-08-23 13:27 ` Daniel Jacobowitz
2002-08-23 13:32   ` Andrew Cagney [this message]
2002-08-24  2:21   ` Eli Zaretskii
2002-08-25 12:17     ` 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=3D669B41.50809@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=drow@mvista.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