From: Diego Novillo <dnovillo@google.com>
To: Jeffrey Yasskin <jyasskin@google.com>
Cc: reply@codereview.appspotmail.com, gcc-patches@gcc.gnu.org
Subject: Re: [google] Merge r173574 to google/gcc-4_6 to fix an incompatibility between C++98 and C++0x (issue4592057)
Date: Tue, 14 Jun 2011 20:27:00 -0000 [thread overview]
Message-ID: <BANLkTin7hunZNjwoy4xc0kGVsYZBXNCXmQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikNi6RbK47vQHdJhfRMHkW+y4jGayJr4khAxRvtZiakEQ@mail.gmail.com>
On Tue, Jun 14, 2011 at 15:59, Jeffrey Yasskin <jyasskin@google.com> wrote:
> It's already in trunk, so my impression was that it was going to be
> automatically merged to google/main. I only need a manual merge to get
> it into our release branches.
Yeah, in this case it's not too different since we'll be switching
google/main to trunk soonish.
OK for google/gcc-4_6.
Diego.
prev parent reply other threads:[~2011-06-14 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 19:04 Jeffrey Yasskin
2011-06-14 19:59 ` Diego Novillo
2011-06-14 20:13 ` Jeffrey Yasskin
2011-06-14 20:27 ` Diego Novillo [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=BANLkTin7hunZNjwoy4xc0kGVsYZBXNCXmQ@mail.gmail.com \
--to=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jyasskin@google.com \
--cc=reply@codereview.appspotmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).