Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: copy-edit File-I/O section of manual
Date: Mon, 15 May 2006 15:09:00 -0000	[thread overview]
Message-ID: <44688908.2040304@codesourcery.com> (raw)
In-Reply-To: <ufyjc4avc.fsf@gnu.org>

Eli Zaretskii wrote:

> If you can present the patch in a way that makes this big picture
> show, it might help me review the patch sooner.  Based on my
> experience, such a presentation will need to use something other than
> Diff, though.

Would it help if I listed some of the changes I made?

* I fixed several spelling errors; e.g., replacing "interupt" with "interrupt", 
"approriate" with "appropriate".
* I fixed several verb tense errors, e.g. replacing "send" with "sent" in many 
places.
* I fixed some places where an adjective was used where an adverb was required, 
e.g., replacing "successful" with "successfully", "reliable" with "reliably".
* There were several places where commas were used incorrectly, often in 
combination with awkward phrasing of the sentence as a whole.  I fixed these.
* I fixed some other instances of awkward grammar, sentence construction, or 
word choice.
* I moved the three sections of text I mentioned in a previous message to 
combine related information in one place.  I updated the section menus to 
reflect these moves.
* I changed the formatting of the sections describing individual calls to use 
@table instead of a mishmash of @smallexample, @exdent, and regular running 
text.  This fixed problems with, for example, the return value descriptions 
being typeset as examples instead of as descriptive text in normal font.
* In combination with the above, I put references to parameters in the running 
text in @var{} and references to function names, type names, and symbolic 
constants in @code{}.

> You are asking me to proofread a large portion of text, instead of
> concentrating on the relatively small differences.

Well, you were complaining that the diffs were too big, and the "large portion" 
of text is only 12 pages.

-Sandra


  reply	other threads:[~2006-05-15 13:57 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
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 [this message]
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=44688908.2040304@codesourcery.com \
    --to=sandra@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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