public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andris Pavenis <andris.pavenis@iki.fi>
To: Jeff Law <law@redhat.com>, DJ Delorie <dj@redhat.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 6/6] [DJGPP] configure.ac: enable LTO
Date: Sat, 09 Jan 2016 07:36:00 -0000	[thread overview]
Message-ID: <5690B88F.2010800@iki.fi> (raw)
In-Reply-To: <56904664.70508@redhat.com>

On 01/09/2016 01:29 AM, Jeff Law wrote:
> On 12/21/2015 11:22 PM, Andris Pavenis wrote:
>> 12/21/2015, 10:00 PM, Jeff Law kirjoitti:
>>> On 12/17/2015 10:51 PM, Andris Pavenis wrote:
>>>> On 12/13/2015 08:12 PM, DJ Delorie wrote:
>>>>>> You can list me as your sponsor.
>>>>> I've been wanting him to be a djgpp target/host maintainer for
>>>>> years anyway, so +1 from me :-)
>>>>>
>>>>>
>>>> Approved part of patches are in (except 6th which I commit after
>>>> 5th)
>>>>
>>>> In middle come a problem with mailing list (collected outgoing
>>>> patches in a batch and did not notice that I had written wrong
>>>> address). Noticed it only after sending when it was too late.
>>> Is there anything in this series that still needs review?
>>>
>>
>> Well. I understood that new version of patch could require new
>> approving. I comments about 5th patch which I took into account in new
>> patch version or responded. There were however no "OK for trunk" or
>> equivalent. Sorry if I'm too pedantic
> No worries.  We're always happy when folks are conservative, particularly when they're just 
> getting engaged with the community.
>
> Can you post the updated #5 patch.  DJ or I will give it a final yes/no so that you can move 
> forward.

It was actually already sent a month ago with comments corresponding review notices::

https://gcc.gnu.org/ml/gcc-patches/2015-12/msg01328.html

Andris


      parent reply	other threads:[~2016-01-09  7:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-05 17:25 Andris Pavenis
2015-12-10 22:32 ` Jeff Law
2015-12-12 16:40   ` Andris Pavenis
2015-12-13 17:01     ` Jeff Law
2015-12-13 18:12       ` DJ Delorie
     [not found]         ` <56739EF4.2040800@wippies.com>
     [not found]           ` <56785A71.3040306@redhat.com>
     [not found]             ` <5678EC40.2040404@iki.fi>
     [not found]               ` <56904664.70508@redhat.com>
2016-01-09  7:36                 ` Andris Pavenis [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=5690B88F.2010800@iki.fi \
    --to=andris.pavenis@iki.fi \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@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).