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: Sun, 14 May 2006 20:12:00 -0000	[thread overview]
Message-ID: <uiro84bjd.fsf@gnu.org> (raw)
In-Reply-To: <446730A4.60300@codesourcery.com> (message from Sandra Loosemore 	on Sun, 14 May 2006 09:29:08 -0400)

> Date: Sun, 14 May 2006 09:29:08 -0400
> From: Sandra Loosemore <sandra@codesourcery.com>
> CC:  gdb-patches@sourceware.org
> 
> Shrug.  If you aren't interested in having a professional writer clean up an 
> abominably-written section of the manual because you can't be bothered to read 
> the revised text, it's your loss, I guess.

I'm sorry to read this, because it's grossly unfair.  I didn't say I
cannot be bothered to read the patches, I said that it's a formidable
job which will have to wait until I have enough free time for it.
When I do have that time, I _will_ read the patch.

I'm grateful for your work, and I don't question your competence in
this matter, but since I'm the responsible person for the manual, you
cannot expect me to blindly approve patches without carefully
reviewing it.

> As I said, the diffs are big because the original text was in such
> bad shape in terms of grammar, spelling, and formatting, not because
> I made any substantive changes to its content.

The problem is, I need to actually see the differences, and you made
it hard for me to do that quickly.  I usually review 99% of changes to
the manual within 24 hours since they are posted, but with such a
jumbo patch where almost every line has one or two words modified, I
gave up after trying to read it for maybe half an hour or so.

Thanks.


  parent reply	other threads:[~2006-05-14 20:07 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
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 [this message]
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=uiro84bjd.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