From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA, doc RFA] Don't install gdb.PYTHONDIR if -nx
Date: Tue, 30 Nov 2010 15:29:00 -0000 [thread overview]
Message-ID: <AANLkTinDY=OdC8C9dMtFF911J2=31kkWe-TmUC8FVZoy@mail.gmail.com> (raw)
In-Reply-To: <E1PNOFq-0005NJ-MM@fencepost.gnu.org>
On Tue, Nov 30, 2010 at 3:20 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Mon, 29 Nov 2010 20:11:07 -0800
>> From: Doug Evans <dje@google.com>
>> Cc: tromey@redhat.com, gdb-patches@sourceware.org
>>
>> --- NEWS 5 Nov 2010 16:55:37 -0000 1.411
>> +++ NEWS 30 Nov 2010 04:09:31 -0000
>> @@ -3,6 +3,10 @@
>>
>> *** Changes since GDB 7.2
>>
>> +* New command line options
>> +
>> +-np Do not initialize the gdb python module.
>> +
>
> Thanks, this is fine.
Thanks.
I think we're now blocked on whether we want "-np" or "-data-directory
/foo" (or some such).
I don't have a strong opinion on either, I like both.
[For reference sake, I've been thinking it would be useful to have an
option to turn off auto-loading of scripts specified in binaries.
But that's a different patch. :-)]
next prev parent reply other threads:[~2010-11-30 15:29 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 [this message]
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
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='AANLkTinDY=OdC8C9dMtFF911J2=31kkWe-TmUC8FVZoy@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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