Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>,  gdb-patches@sourceware.org
Subject: Re: PATCH: copy-edit File-I/O section of manual
Date: Sun, 14 May 2006 19:44:00 -0000	[thread overview]
Message-ID: <44676486.8090002@codesourcery.com> (raw)
In-Reply-To: <20060514150059.GA29094@nevyn.them.org>

Daniel Jacobowitz wrote:
> 
> Shh... let's all take a deep breath, yes?  Eli, I realize it will have
> to wait until you can find the time, but could you look at Sandra's
> revised text at some point?  Better later than never.
> 

Thanks, Daniel.  On reflection, I think Eli and I are just thinking at 
cross-purposes here.  Eli is worried about what has changed at a line-by-line 
level, while I have been thinking in terms of the "big picture" of bringing the 
writing in this section as a whole up to an acceptable standard of quality for a 
professional document.  Are there other mistakes I may have missed or different 
formatting or font conventions that should be applied consistently throughout 
the section?  That's why I suggested applying the patch and proofreading the 
resulting text.

-Sandra


  reply	other threads:[~2006-05-14 17:09 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 [this message]
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=44676486.8090002@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