From: Tristan Gingold <gingold@adacore.com>
To: "Eggone, NagaJyothi" <NagaJyothi.Eggone@amd.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>,
"Ekanathan, Saravanan" <Saravanan.Ekanathan@amd.com>
Subject: Re: Release 2.23: Ping #2
Date: Tue, 11 Sep 2012 09:20:00 -0000 [thread overview]
Message-ID: <BC95FBEE-2F8B-460E-95FB-2638B89DE3B7@adacore.com> (raw)
In-Reply-To: <80417A078608EC4BBFDAFAE7DF706EC519C7B8@sausexdag05.amd.com>
On Sep 11, 2012, at 8:47 AM, Eggone, NagaJyothi wrote:
> Hi Tristan,
>
> You might have missed this request for backport to 2.23 I made last week. If it is not too late, please backport these two patches to the 2.23 branch. The patches are:
> 1)PR14423 fix - http://sourceware.org/ml/binutils-cvs/2012-08/msg00075.html
> 2) Btver1 and Btver2 enablement patch
> http://sourceware.org/ml/binutils-cvs/2012-08/msg00127.html
Yes, this patch is still on my list. Thank you for providing the binutils-cvs url.
Tristan.
next prev parent reply other threads:[~2012-09-11 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 6:47 FW: " Eggone, NagaJyothi
2012-09-11 9:20 ` Tristan Gingold [this message]
2012-09-13 3:40 ` Doug Kwan (關振德)
2012-09-13 7:41 ` Tristan Gingold
2012-09-13 16:57 ` Doug Kwan (關振德)
2012-09-18 12:23 ` Tristan Gingold
-- strict thread matches above, loose matches on Subject: below --
2012-09-17 11:05 Walter Lee
2012-09-17 18:34 ` Walter Lee
2012-09-18 12:27 ` Tristan Gingold
2012-09-06 15:02 Eggone, NagaJyothi
2012-07-23 12:41 Release 2.23 Tristan Gingold
2012-07-31 20:30 ` Matthias Klose
2012-08-01 13:59 ` Tristan Gingold
2012-08-01 14:03 ` Richard Earnshaw
2012-08-01 14:35 ` Tristan Gingold
2012-08-01 14:40 ` Richard Earnshaw
2012-08-02 11:41 ` Tristan Gingold
2012-08-31 14:40 ` Release 2.23: Ping Tristan Gingold
2012-09-05 9:02 ` Release 2.23: Ping #2 Tristan Gingold
2012-09-07 3:14 ` Alan Modra
2012-09-09 17:05 ` Hans-Peter Nilsson
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=BC95FBEE-2F8B-460E-95FB-2638B89DE3B7@adacore.com \
--to=gingold@adacore.com \
--cc=NagaJyothi.Eggone@amd.com \
--cc=Saravanan.Ekanathan@amd.com \
--cc=binutils@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).