From: dnovillo@google.com
To: gchare@google.com, crowl@google.com, gdr@integrable-solutions.net
Cc: gcc-patches@gcc.gnu.org, reply@codereview.appspotmail.com
Subject: Re: [pph] Fix binding_level's names_size streaming (issue4634071)
Date: Fri, 24 Jun 2011 20:05:00 -0000 [thread overview]
Message-ID: <20cf303ea674dd040404a679e0f1@google.com> (raw)
On 2011/06/24 17:35:51, Gabriel Charette wrote:
> This was commited to trunk. Diego can you commit this patch to pph as
well?
Done. r175387.
Diego.
http://codereview.appspot.com/4634071/
next reply other threads:[~2011-06-24 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 20:05 dnovillo [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-23 0:17 Gabriel Charette
2011-06-23 2:20 ` Gabriel Charette
2011-06-23 4:55 ` Gabriel Dos Reis
2011-06-23 11:33 ` Diego Novillo
2011-06-24 18:29 ` Gabriel Charette
2011-06-23 0:06 Gabriel Charette
2011-06-21 1:39 Gabriel Charette
2011-06-22 18:36 ` Diego Novillo
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=20cf303ea674dd040404a679e0f1@google.com \
--to=dnovillo@google.com \
--cc=crowl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gchare@google.com \
--cc=gdr@integrable-solutions.net \
--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).