public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Steven Bosscher <stevenb.gcc@gmail.com>,
	 gcc-patches@gcc.gnu.org,   Jan Hubicka <hubicka@ucw.cz>,
	  iant@google.com
Subject: Re: Patch ping (
Date: Sun, 22 Apr 2007 22:52:00 -0000	[thread overview]
Message-ID: <462BE6C6.3000507@codesourcery.com> (raw)
In-Reply-To: <84fc9c000704221023x1ece5ed9ja6d87b846e88545c@mail.gmail.com>

Richard Guenther wrote:
> On 4/21/07, Steven Bosscher <stevenb.gcc@gmail.com> wrote:
>> On Wednesday 18 April 2007 02:18, Jan Hubicka wrote:
>> > Hi,
>> > I would like to ping the patch
>> > http://gcc.gnu.org/ml/gcc-patches/2007-03/msg01169.html
>> > that removes line nmuber notes from RTL.  I think it is quite important
>> > cleanup and would like it to receive testing within mainline for some
>> > period of time.
>>
>> I think this is a really nice cleanup.  It's a shame that no-one has
>> approved this work yet.
>>
>> The patch looks OK to me, but I can of course not approve it.
> 
> I looked over the patch and I agree it's ok.  So, if nobody objects this
> patch is ok for mainline (approving a patch for a part of gcc that I'm not
> too familiar with).

For avoidance of doubt, I hereby approve the patch.

Thanks,

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

WARNING: multiple messages have this Message-ID

From: Mark Mitchell <mark@codesourcery.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Steven Bosscher <stevenb.gcc@gmail.com>,
	 gcc-patches@gcc.gnu.org,   Jan Hubicka <hubicka@ucw.cz>,
	  iant@google.com
Subject: Re: Patch ping (
Date: Sun, 22 Apr 2007 23:08:00 -0000	[thread overview]
Message-ID: <462BE6C6.3000507@codesourcery.com> (raw)
Message-ID: <20070422230800.gd01JToMoJejMu1C-ZbWGI8UkqDYFspMHKl_Ri5mSYs@z> (raw)
In-Reply-To: <84fc9c000704221023x1ece5ed9ja6d87b846e88545c@mail.gmail.com>

Richard Guenther wrote:
> On 4/21/07, Steven Bosscher <stevenb.gcc@gmail.com> wrote:
>> On Wednesday 18 April 2007 02:18, Jan Hubicka wrote:
>> > Hi,
>> > I would like to ping the patch
>> > http://gcc.gnu.org/ml/gcc-patches/2007-03/msg01169.html
>> > that removes line nmuber notes from RTL.  I think it is quite important
>> > cleanup and would like it to receive testing within mainline for some
>> > period of time.
>>
>> I think this is a really nice cleanup.  It's a shame that no-one has
>> approved this work yet.
>>
>> The patch looks OK to me, but I can of course not approve it.
> 
> I looked over the patch and I agree it's ok.  So, if nobody objects this
> patch is ok for mainline (approving a patch for a part of gcc that I'm not
> too familiar with).

For avoidance of doubt, I hereby approve the patch.

Thanks,

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

  reply	other threads:[~2007-04-22 22:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-18  1:07 Patch ping Jan Hubicka
2007-04-21 21:17 ` Patch ping ( Steven Bosscher
2007-04-22 19:02   ` Richard Guenther
2007-04-22 22:52     ` Mark Mitchell [this message]
2007-04-22 23:08       ` Mark Mitchell

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=462BE6C6.3000507@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=iant@google.com \
    --cc=richard.guenther@gmail.com \
    --cc=stevenb.gcc@gmail.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).