From: Joel Brobecker <brobecker@adacore.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Daniel Jacobowitz <dan@codesourcery.com>,
gdb-patches@sourceware.org, gdb@sourceware.org,
vladimir@codesourcery.com
Subject: Re: [patch] Re: -data-list-register-names regression?
Date: Thu, 18 Mar 2010 13:55:00 -0000 [thread overview]
Message-ID: <20100318135509.GI3830@adacore.com> (raw)
In-Reply-To: <201003181328.o2IDSD0D000501@d12av02.megacenter.de.ibm.com>
> OK, I've checked this in to mainline now. It seems reasonable to me
> to put this in 7.1 as well, but I think you have final call on that ...
> If you'd like me to put in, please let me know.
OK, if we both agree that it's safe enough to go into 7.1, then let's
apply it on the branch as well.
Thanks!
--
Joel
next prev parent reply other threads:[~2010-03-18 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201003171345.44000.vladimir@codesourcery.com>
2010-03-17 21:38 ` Ulrich Weigand
2010-03-17 22:37 ` Daniel Jacobowitz
2010-03-17 22:59 ` Joel Brobecker
2010-03-18 4:44 ` Dave Korn
2010-03-18 13:28 ` Ulrich Weigand
2010-03-18 13:55 ` Joel Brobecker [this message]
2010-03-18 15:53 ` Ulrich Weigand
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=20100318135509.GI3830@adacore.com \
--to=brobecker@adacore.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=uweigand@de.ibm.com \
--cc=vladimir@codesourcery.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