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: Mon, 15 May 2006 20:44:00 -0000 [thread overview]
Message-ID: <uy7x32f6t.fsf@gnu.org> (raw)
In-Reply-To: <44688908.2040304@codesourcery.com> (message from Sandra Loosemore on Mon, 15 May 2006 09:58:32 -0400)
> Date: Mon, 15 May 2006 09:58:32 -0400
> From: Sandra Loosemore <sandra@codesourcery.com>
> CC: gdb-patches@sourceware.org
>
> Would it help if I listed some of the changes I made?
Thanks for taking time to write it. I actually already figured out
this much, what I need is some easy way to find only the different
words and phrases in the line-by-line diff-style output, which in this
case makes this job much harder.
When I do get to this, I will probably use Emacs's Ediff or some such,
which shows the modified parts within each line.
> Well, you were complaining that the diffs were too big, and the "large portion"
> of text is only 12 pages.
12 pages is quite a lot for my limited time, and I will need to read
the surrounding chapters and sections as well, to see how well the new
arrangement fits into the overall organization of the manual.
Thanks.
next prev parent reply other threads:[~2006-05-15 20:43 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 [this message]
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=uy7x32f6t.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