From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>, gdb-patches@sourceware.org
Subject: Re: Fix gdb 7.0 compilation on IRIX 5.3
Date: Tue, 24 Nov 2009 17:32:00 -0000 [thread overview]
Message-ID: <m3pr7725is.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20091123223334.GC5595@adacore.com> (Joel Brobecker's message of "Mon, 23 Nov 2009 17:33:34 -0500")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>> Could you check this in for me? I couldn't check out an rw cvs tree from
>> sourceware.org, although I should have rw access to src.
Joel> Someone beat me to it, but I confirm that this change has been checked
Joel> in HEAD.
Joel> How about the 7.0 branch?
I just committed it there as well.
Tom
prev parent reply other threads:[~2009-11-24 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 18:54 Rainer Orth
2009-11-23 20:19 ` Tom Tromey
2009-11-23 20:45 ` Rainer Orth
2009-11-23 21:35 ` Tom Tromey
2009-11-23 21:42 ` Rainer Orth
2009-11-23 22:33 ` Joel Brobecker
2009-11-24 17:32 ` 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=m3pr7725is.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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