public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@redhat.com>
To: Allan McRae <allan@archlinux.org>,
	Florian Weimer <fweimer@redhat.com>,
	Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v1.1] __gconv_translit_find: Actually append ".so" to module name [BZ #17187]
Date: Tue, 26 Aug 2014 16:46:00 -0000	[thread overview]
Message-ID: <53FCB9D6.6030002@redhat.com> (raw)
In-Reply-To: <53FC9AB0.6020400@redhat.com>

On 08/26/2014 10:33 AM, Carlos O'Donell wrote:
> On 08/26/2014 07:23 AM, Allan McRae wrote:
>> On 26/08/14 19:52, Florian Weimer wrote:
>>> On 08/26/2014 08:35 AM, Siddhesh Poyarekar wrote:
>>>
>>>> I think this fix is fine (except a minor nit below), but it would be
>>>
>>> Thanks.
>>>
>>>> good if another maintainer also verifies that it won't break anything.
>>>> Also, Allan needs to ack it for 2.20.  I am going to put the patch in
>>>> rawhide today anyway, so I'll report back if there are any issues; I
>>>> don't expect any though.
>>>
>>> Okay, I will reword the comment.
>>>
>>> Allan, is this okay for 2.20/current master?
>>>
>>
>> I'd like the "if another maintainer also verifies that it won't break
>> anything" to be enacted.  My best guess is that it is fine and given
>> there is an exploit it should go in, but I am not confident enough about
>> lack of side effects.
>>
>> Can someone else give this an ack?  Roland, Carlos, Joseph, etc?
>>
>> Once that is done, it is fine to commit to master.
> 
> I'm reviewing.

Review done. Looks good to me, one nit.

c.

  reply	other threads:[~2014-08-26 16:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 13:01 [PATCH] " Florian Weimer
2014-07-28 23:02 ` Roland McGrath
2014-07-29  5:50   ` Florian Weimer
     [not found]     ` <CAJ_zFkJLdEpJzKSM3HDN6PuVriTd4vKNqq=EubtCR5qqvt1U8g@mail.gmail.com>
2014-07-29 19:05       ` Florian Weimer
2014-07-31 18:09         ` Tavis Ormandy
2014-07-31 20:29           ` Joseph S. Myers
2014-08-08 15:34   ` Florian Weimer
2014-08-21 17:33 ` [PATCH v1.1] " Florian Weimer
2014-08-26  6:35   ` Siddhesh Poyarekar
2014-08-26  9:52     ` Florian Weimer
2014-08-26 11:23       ` Allan McRae
2014-08-26 14:33         ` Carlos O'Donell
2014-08-26 16:46           ` Carlos O'Donell [this message]
2014-08-26 12:09   ` Andreas Schwab
2014-08-26 12:25     ` Florian Weimer
2014-08-26 14:36       ` Carlos O'Donell
2014-08-26 16:45   ` Carlos O'Donell
2014-08-26 16:55     ` Florian Weimer
2014-08-26 17:54       ` Carlos O'Donell
2014-08-26 18:45       ` Florian Weimer

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=53FCB9D6.6030002@redhat.com \
    --to=carlos@redhat.com \
    --cc=allan@archlinux.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@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).