From: Tom Tromey <tromey@redhat.com>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] New function finish_python_initialization
Date: Mon, 01 Nov 2010 20:25:00 -0000 [thread overview]
Message-ID: <m37hgwaiu0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20101101022638.812792461AF@ruffy.mtv.corp.google.com> (Doug Evans's message of "Sun, 31 Oct 2010 19:26:38 -0700 (PDT)")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> This patch fixes things by moving the evaluation of the init
Doug> python script to after most of the gdb initialization. That way
Doug> the python script can punt on further such issues.
Doug> I will check this in in two days if there are no objections.
It looks ok to me.
Tom
prev parent reply other threads:[~2010-11-01 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 2:26 Doug Evans
2010-11-01 20:25 ` Tom Tromey [this message]
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=m37hgwaiu0.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).