From: David Miller <davem@redhat.com>
To: ebotcazou@adacore.com
Cc: rearnsha@arm.com, gcc@gcc.gnu.org, kazu@codesourcery.com,
rth@redhat.com, jakub@redhat.com
Subject: Re: Preparing to merge ARM/hard_vfp_branch to trunk
Date: Wed, 05 Aug 2009 21:15:00 -0000 [thread overview]
Message-ID: <20090805.124450.16393101.davem@redhat.com> (raw)
In-Reply-To: <200908051759.02080.ebotcazou@adacore.com>
From: Eric Botcazou <ebotcazou@adacore.com>
Date: Wed, 5 Aug 2009 17:59:01 +0200
>> I believe that I could legitimately approve that patch myself (it's
>> pretty trivial and I didn't author it), but I'd prefer to get approval
>> from one of the SPARC maintainers. Here's your chance:
>>
>> http://gcc.gnu.org/ml/gcc-patches/2009-04/msg01027.html
>
> OK.
It looks fine to me too.
next prev parent reply other threads:[~2009-08-05 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 15:28 Richard Earnshaw
2009-08-05 16:47 ` Eric Botcazou
2009-08-05 21:15 ` David Miller [this message]
2009-08-06 14:21 ` Joseph S. Myers
2009-08-06 19:35 ` Richard Earnshaw
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=20090805.124450.16393101.davem@redhat.com \
--to=davem@redhat.com \
--cc=ebotcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kazu@codesourcery.com \
--cc=rearnsha@arm.com \
--cc=rth@redhat.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).