From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org,
"Sérgio Durigan Júnior" <sergiodj@br.ibm.com>
Subject: Re: Python pretty-printing [1/6]
Date: Fri, 03 Apr 2009 20:39:00 -0000 [thread overview]
Message-ID: <m3k5618oas.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090403191407.GA10599@caradoc.them.org> (Daniel Jacobowitz's message of "Fri\, 3 Apr 2009 15\:14\:07 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Daniel> FWIW, I think it shouldn't even be a maint command. We can set
Daniel> debug-file-directory and sysroot, why not datadir?
Good point. I renamed it to "set datadir".
I think I will put the docs for this in a later patch.
At least with the current gdb, it seems to make the most sense to have
the documentation for this new parameter located near the sole user of
it; but that node doesn't appear until patch #2.
I also noticed that some of the code in patch #1 is actually not
really related to this feature. All the pythondir stuff will be gone
in the next revision; I'll send this as soon as I fix up the README.
Tom
next prev parent reply other threads:[~2009-04-03 20:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 20:54 Tom Tromey
2009-04-03 14:23 ` Eli Zaretskii
2009-04-03 15:46 ` Tom Tromey
2009-04-03 17:13 ` Eli Zaretskii
2009-04-04 21:43 ` Thiago Jung Bauermann
2009-04-05 3:12 ` Eli Zaretskii
2009-04-03 18:29 ` Tom Tromey
2009-04-03 19:14 ` Daniel Jacobowitz
2009-04-03 20:39 ` Tom Tromey [this message]
2009-04-03 15:23 ` Daniel Jacobowitz
2009-04-03 23:58 ` Tom Tromey
2009-04-04 3:30 ` Daniel Jacobowitz
2009-04-04 16:16 ` Tom Tromey
2009-04-04 9:10 ` Eli Zaretskii
2009-04-06 17:45 ` Tom Tromey
2009-04-06 20:38 ` Eli Zaretskii
2009-04-07 18:52 ` Daniel Jacobowitz
2009-04-07 18:24 ` Joel Brobecker
2009-04-07 18:43 ` 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=m3k5618oas.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@br.ibm.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