From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [doc RFA]: New option --with-iconv-bin
Date: Mon, 09 May 2011 21:08:00 -0000 [thread overview]
Message-ID: <BANLkTim2+X4jX-Fuwr+Q-uyszzriAL0ogA@mail.gmail.com> (raw)
In-Reply-To: <8339knipbj.fsf@gnu.org>
On Mon, May 9, 2011 at 1:36 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Mon, 9 May 2011 13:19:56 -0700
>> From: Doug Evans <dje@google.com>
>> Cc: gdb-patches@sourceware.org
>>
>> > Why not just say "if your @command{iconv} program is installed in a
>> > non-standard place, you will need to tell @value{GDBN} where to find
>> > it."?
>> >
>>
>> The iconv program comes from glibc, but you're right, it doesn't
>> *necessarily* come from there.
>>
>> How about this?
>
> It's fine, but...
>
>> +If @value{GDBN} is using the @code{iconv} program and it is installed in
>> +a non-standard place, you will need to tell @value{GDBN} where to find it.
>
> The first "it" is ambiguous: it could have meant GDB or iconv.
Yeah, I recognized the ambiguity in earlier versions and explicitly
tried a couple of variations to avoid the ambiguity.
I like what I came up with but it can always be improved of course.
> Suggest a slight rephrase:
>
> If @value{GDBN} is using the @code{iconv} program which is installed
> in a non-standard place, ...
Ok.
next prev parent reply other threads:[~2011-05-09 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 18:20 Doug Evans
2011-05-09 19:09 ` Eli Zaretskii
2011-05-09 20:34 ` Doug Evans
[not found] ` <BANLkTikvtS3eSk_8e+40X5ky9h_HEX5VNQ@mail.gmail.com>
2011-05-09 20:36 ` Eli Zaretskii
2011-05-09 21:08 ` Doug Evans [this message]
2011-05-09 21:53 ` Doug Evans
2011-05-09 19:41 ` Tom Tromey
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=BANLkTim2+X4jX-Fuwr+Q-uyszzriAL0ogA@mail.gmail.com \
--to=dje@google.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