From: Diego Novillo <dnovillo@google.com>
To: Benjamin Kosnik <bkoz@redhat.com>
Cc: reply@codereview.appspotmail.com, dougkwan@google.com,
libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [google] Install cpu_defines.h (issue4440044)
Date: Tue, 19 Apr 2011 16:42:00 -0000 [thread overview]
Message-ID: <BANLkTiknZgwibj3O4gZSx1-mEBTUfju_mQ@mail.gmail.com> (raw)
In-Reply-To: <20110419090419.6c55568b@shotwell>
On Tue, Apr 19, 2011 at 12:04, Benjamin Kosnik <bkoz@redhat.com> wrote:
>
>> This patch adds cpu_defines.h to the set of files to be installed.
>> Doug, could you describe why we need to do this? Will you be
>> submitting this patch for trunk?
>
> It's already in trunk, see
D'oh. Thanks. Clearly, I was no autopilot. Doug even said so in the
internal patch tracking tool.
Diego.
next prev parent reply other threads:[~2011-04-19 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 22:11 Diego Novillo
2011-04-19 16:38 ` Benjamin Kosnik
2011-04-19 16:42 ` Diego Novillo [this message]
2011-04-19 17:38 ` Doug Kwan (關振德)
2011-04-19 17:49 ` Paolo Carlini
2011-04-19 18:20 ` Doug Kwan (關振德)
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=BANLkTiknZgwibj3O4gZSx1-mEBTUfju_mQ@mail.gmail.com \
--to=dnovillo@google.com \
--cc=bkoz@redhat.com \
--cc=dougkwan@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--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).