From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA, RFA 7.6] Improve help for, e.g., running gdb in build tree.
Date: Wed, 27 Mar 2013 20:17:00 -0000 [thread overview]
Message-ID: <87y5d8elic.fsf@fleche.redhat.com> (raw)
In-Reply-To: <yjt2620c6675.fsf@ruffy2.mtv.corp.google.com> (Doug Evans's message of "Wed, 27 Mar 2013 11:36:14 -0700")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> 2013-03-27 Doug Evans <dje@google.com>
Doug> * python/python.c (finish_python_initialization): Provide suggestion
Doug> for how to tell gdb to find its python files.
It looks reasonable to me.
Tom
next prev parent reply other threads:[~2013-03-27 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 20:17 Doug Evans
2013-03-27 20:17 ` Tom Tromey [this message]
2013-03-27 20:44 ` Doug Evans
2013-03-28 12:00 ` Joel Brobecker
2013-03-28 19:46 ` Doug Evans
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=87y5d8elic.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--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