Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: bwilson@tensilica.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] fix hyphenation and matters of style in docs
Date: Tue, 10 Apr 2007 19:22:00 -0000	[thread overview]
Message-ID: <ulkh0kpbc.fsf@gnu.org> (raw)
In-Reply-To: <20070410154030.GF10890@caradoc.them.org> (message from Daniel 	Jacobowitz on Tue, 10 Apr 2007 11:40:30 -0400)

> > 
> > 2007-03-26  Bob Wilson  <bob.wilson@acm.org>
> > 	
> > 	* gdb.texinfo (Contributors, Continuing and Stepping)
> > 	(Fortran Defaults, HPPA, TUI, TUI Commands, Configure Options)
> > 	(General Query Packets, File-I/O remote protocol extension)
> > 	(Protocol basics, The F reply packet, write)
> > 	(Protocol-specific representation of datatypes, Memory transfer):
> > 	Fix hyphenation, punctuation and grammar problems.
> > 	(Cygwin Native): Likewise.  Also fix misuse of @pxref and use
> > 	'section' instead of 'subsection' in the text.
> > 	(Non-debug DLL symbols): Avoid 'subsubsection' in the text.
> > 	(i386): Remove period from section name.
> 
> Eli, did you see this patch?

Either I didn't see or somehow managed to delete it inadvertently,
since I don't have it in my INBOX.  Sorry for that.

Reviewing it now, I agree with the suggested changes, but have a few
questions/requests:

 . Please replace "@code{configure}" with "@file{configure}" or
   "@command{configure}".

 . I don't understand this change:

    -@item F@var{retcode},@var{errno},@var{Ctrl-C flag};@var{call specific attachment}
    +@item F@var{retcode},@var{errno},@var{Ctrl-C flag};@var{call specific
    +attachment}

   Maybe you wanted to say "call-specific attachment"? if so, I agree.

 . Since this patch was posted, the section names were rewritten to
   use a consistent capitalization, but this one doesn't:

    +@subsection Protocol-specific representation of datatypes

With these gotchas taken care of, Bob, please commit the patch, and
thanks.

And thanks to Daniel for the heads-up.


  reply	other threads:[~2007-04-10 19:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 17:08 Bob Wilson
2007-04-10 15:40 ` Daniel Jacobowitz
2007-04-10 19:22   ` Eli Zaretskii [this message]
2007-04-11 18:52     ` Bob Wilson

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=ulkh0kpbc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bwilson@tensilica.com \
    --cc=drow@false.org \
    --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