Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: copy-edit File-I/O section of manual
Date: Sat, 13 May 2006 19:03:00 -0000	[thread overview]
Message-ID: <u4pzt69f3.fsf@gnu.org> (raw)
In-Reply-To: <4465ED4D.4020505@codesourcery.com> (message from Sandra 	Loosemore on Sat, 13 May 2006 10:29:33 -0400)

> Date: Sat, 13 May 2006 10:29:33 -0400
> From: Sandra Loosemore <sandra@codesourcery.com>
> 
> When I was implementing the File-I/O protocol recently, I noticed a lot of 
> spelling and grammatical mistakes in that section of the manual.  Here's a patch 
> to clean it up.

Thanks.  However, could you please submit these as two separate
patches, one that fixes only the spelling and grammar, the other with
the rest?  I'd like to understand the motivation for moving stuff
around, for starters.

Also, when you send the patch for spelling and grammar, please try not
to reformat lines, so that unmodified lines don't appear in the diffs.
The way you did it (refilling the paragraphs after changing them)
makes the diffs unnecessarily voluminous and hard to read.

TIA

> 2006-05-13  Sandra Loosemore  <sandra@codesourcery.com>
> 	* gdb.texinfo (File-I/O remote protocol extension): General
> 	copy-editing to fix spelling, grammar, formatting issues.
> 	Moved a few paragraphs around to more logical places.

The ChangeLog entries should mention the node name for each change; it
is not sufficient to name only their parent node.

> ! The File-I/O protocol uses the @code{F} packet as the request as well
>   as as reply packet.
    ^^^^^
This is still not right.

Thanks again for working on this.


  reply	other threads:[~2006-05-13 18:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-13 14:32 Sandra Loosemore
2006-05-13 19:03 ` Eli Zaretskii [this message]
2006-05-14  3:29   ` Sandra Loosemore
2006-05-14  6:35     ` Eli Zaretskii
2006-05-14 15:01       ` Sandra Loosemore
2006-05-14 15:10         ` Daniel Jacobowitz
2006-05-14 19:44           ` Sandra Loosemore
2006-05-14 22:06             ` Eli Zaretskii
2006-05-15 15:09               ` Sandra Loosemore
2006-05-15 20:44                 ` Eli Zaretskii
2006-05-14 20:15           ` Eli Zaretskii
2006-05-14 20:21             ` Daniel Jacobowitz
2006-05-14 20:12         ` Eli Zaretskii
2006-06-09 19:43 ` Eli Zaretskii
2006-06-10 18:50   ` Sandra Loosemore
2006-06-10 21:34     ` 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=u4pzt69f3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sandra@codesourcery.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