From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA, doc RFA] Don't install gdb.PYTHONDIR if -nx
Date: Mon, 06 Dec 2010 20:58:00 -0000 [thread overview]
Message-ID: <AANLkTikT2_EpGkhd2sVZmcuRmXv4iDShkJSUaHG7A1PT@mail.gmail.com> (raw)
In-Reply-To: <83sjya39sn.fsf@gnu.org>
On Mon, Dec 6, 2010 at 12:50 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Mon, 6 Dec 2010 12:43:02 -0800
>> From: Doug Evans <dje@google.com>
>> Cc: gdb-patches@sourceware.org
>>
>> Eli, can I have a doc RFA.
>
> Sure.
>
>> +* New command line options
>> +
>> +-data-directory DIR Specify DIR as the "data-directory".
>> +
>
> How about saying what is this directory good for?
>
>> +@item -data-directory @var{directory}
>> +@cindex @code{--data-directory}
>> +Run @value{GDBN} using @var{directory} as its data-directory.
>> +The data-directory is where @value{GDBN} searches for its
>> +auxiliary files.
>
> Same here: what "auxiliary files" are those? Without knowing that,
> there's no chance users will benefit from this option.
This is mostly just for testing, so I punted.
But ok. Ideally I'd just include a reference to the docs for "set
data-directory" or --with-gdb-datadir, but those don't say much
either. Blech.
next prev parent reply other threads:[~2010-12-06 20:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 0:40 [RFA] " Doug Evans
2010-11-29 21:38 ` Tom Tromey
2010-11-30 0:03 ` [RFA, doc RFA] " Doug Evans
2010-11-30 0:30 ` Jan Kratochvil
2010-11-30 3:54 ` Eli Zaretskii
2010-11-30 4:11 ` Doug Evans
2010-11-30 11:20 ` Eli Zaretskii
2010-11-30 15:29 ` Doug Evans
2010-11-30 18:59 ` Tom Tromey
2010-12-06 20:43 ` Doug Evans
2010-12-06 20:50 ` Eli Zaretskii
2010-12-06 20:58 ` Doug Evans [this message]
2010-12-06 21:15 ` Doug Evans
2010-12-06 21:15 ` Eli Zaretskii
2010-12-06 21:16 ` Doug Evans
2010-12-06 22:17 ` Doug Evans
2010-12-07 4:02 ` Eli Zaretskii
2010-12-07 1:38 ` Jan Kratochvil
2010-11-30 4:22 ` [RFA] " Daniel Jacobowitz
2010-11-30 5:16 ` Doug Evans
2010-11-30 18:19 ` Daniel Jacobowitz
2010-11-30 18:25 ` Doug Evans
2010-11-30 5:33 ` Jan Kratochvil
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=AANLkTikT2_EpGkhd2sVZmcuRmXv4iDShkJSUaHG7A1PT@mail.gmail.com \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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