Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kai Tietz <ktietz70@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>, Nick Clifton <nickc@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
		"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Fix a MinGW warning in libiberty/strerror.c
Date: Fri, 16 Jan 2015 11:56:00 -0000	[thread overview]
Message-ID: <CAEwic4YS8+t7JdUja+7i4kHPJQ61wJLYpM4_JgtxC1yOsfWKUQ@mail.gmail.com> (raw)
In-Reply-To: <83vbk70wsz.fsf@gnu.org>

2015-01-16 12:50 GMT+01:00 Eli Zaretskii <eliz@gnu.org>:
>> Date: Fri, 16 Jan 2015 12:34:25 +0100
>> From: Kai Tietz <ktietz70@googlemail.com>
>> Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
>>       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>>
>> Hi Eli,
>>
>> patch is reasonable and ok for me.
>
> Thanks.  Do I need to hear from someone else approving this, or can I
> go ahead and commit?

Well, from POV of the Windows-maintainer in gcc, the patch is ok.  As
libiberty is shared with other ventures, you might want to get an ok
by other ventures, too.

I would say, as long as there are no objections - and there weren't
any now for some time this patch waiting for comments - I would go
ahead and say patch is ok.

Regards,
Kai


  reply	other threads:[~2015-01-16 11:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02 10:54 Eli Zaretskii
2015-01-16 11:18 ` Eli Zaretskii
2015-01-16 11:34   ` Kai Tietz
2015-01-16 11:49     ` Eli Zaretskii
2015-01-16 11:56       ` Kai Tietz [this message]
2015-01-16 21:39       ` DJ Delorie
2015-01-17  9:44         ` Eli Zaretskii

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=CAEwic4YS8+t7JdUja+7i4kHPJQ61wJLYpM4_JgtxC1yOsfWKUQ@mail.gmail.com \
    --to=ktietz70@googlemail.com \
    --cc=eliz@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@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