From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: archer@sourceware.org, "Paul Pluzhnikov" <ppluzhnikov@google.com>,
gdb-patches@sourceware.org
Subject: Re: Make GDB build with python 2.4 again.
Date: Mon, 20 Oct 2008 00:38:00 -0000 [thread overview]
Message-ID: <m34p38cdc6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200810200127.25864.pedro@codesourcery.com> (Pedro Alves's message of "Mon\, 20 Oct 2008 01\:27\:25 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
>> Would you mind updating gdbint.texinfo to say that?
Pedro> That sounds fair. I'll do that.
Thanks.
Pedro> However, I'm also fine with reverting my last change, and
Pedro> applying Paul's if that's less work for you. Heck, that's why we
Pedro> use a revision control system.
>> Forward! I'll just fix the branch.
Pedro> Thanks.
I pushed the changes to python branch.
Tom
prev parent reply other threads:[~2008-10-20 0:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 20:18 Pedro Alves
2008-10-19 22:47 ` Paul Pluzhnikov
2008-10-19 23:17 ` Pedro Alves
2008-10-19 23:43 ` Tom Tromey
2008-10-20 0:06 ` Pedro Alves
2008-10-20 0:14 ` Tom Tromey
2008-10-20 0:27 ` Pedro Alves
2008-10-20 0:38 ` 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=m34p38cdc6.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=ppluzhnikov@google.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