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 22:06:00 -0000 [thread overview]
Message-ID: <ufyjc4avc.fsf@gnu.org> (raw)
In-Reply-To: <44676486.8090002@codesourcery.com> (message from Sandra Loosemore on Sun, 14 May 2006 13:10:30 -0400)
> Date: Sun, 14 May 2006 13:10:30 -0400
> From: Sandra Loosemore <sandra@codesourcery.com>
>
> 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.
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.
> That's why I suggested applying the patch and proofreading the
> resulting text.
You are asking me to proofread a large portion of text, instead of
concentrating on the relatively small differences. This is precisely
the large job which I'm trying to avoid as much as possible, because
it takes so much more time. That is why I prefer small, isolated
diffs that can be approved without re-reading entire chapters. By
contrast, significant changes that rearrange the material absolutely
_require_ to consider the overall effect of the structural changes,
which means I need to read, or at least skim, across large portions of
the manual, and consider didactic issues in addition to purely
linguistic, grammatic, and markup-related aspects.
next prev parent reply other threads:[~2006-05-14 20:21 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 [this message]
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=ufyjc4avc.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