From: Carlos O'Donell <carlos@redhat.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>,
libc-alpha@sourceware.org
Subject: Re: [PING^5][PATCH v10 0/5][BZ 10871] Month names in alternative grammatical case
Date: Mon, 08 Jan 2018 18:20:00 -0000 [thread overview]
Message-ID: <d5a99d06-1db3-7f75-c5af-3e090cf31c3c@redhat.com> (raw)
In-Reply-To: <1306580936.612201.1515406139914@poczta.nazwa.pl>
On 01/08/2018 02:08 AM, Rafal Luzynski wrote:
> 21.12.2017 02:48 Carlos O'Donell <carlos@redhat.com> wrote:
>>
>>
>> On 12/20/2017 04:30 PM, Rafal Luzynski wrote:
>>> PING^4
>>>
>>> With these changes, [7] can I assume that the reviews so far are
>>> sufficient and I should commit this week?
>>
>> Your patches are on the "desirable this release" list:
>> https://sourceware.org/glibc/wiki/Release/2.27#Desirable_this_release.3F
>>
>> This means it should get one more review before commit for 2.27.
>> [...]
>
> PING^5
>
> Although my patches are on the "desirable this release" list it's
> also likely they will be deferred to 2.28 if there are no more
> reviews.
>
> Sorry for my impatience but we are really short of time.
Where are the final set of patches?
Could you please post the patch set to the list so I can review those?
--
Cheers,
Carlos.
next prev parent reply other threads:[~2018-01-08 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 11:43 [PATCH " Rafal Luzynski
2017-11-30 11:37 ` [PING][PATCH " Rafal Luzynski
2017-12-06 22:33 ` [PING^2][PATCH " Rafal Luzynski
2017-12-12 22:49 ` [PING^3][PATCH " Rafal Luzynski
2017-12-21 0:30 ` [PING^4][PATCH " Rafal Luzynski
2017-12-21 1:48 ` Carlos O'Donell
2017-12-21 21:05 ` Rafal Luzynski
2018-01-08 10:09 ` [PING^5][PATCH " Rafal Luzynski
2018-01-08 18:20 ` Carlos O'Donell [this message]
2018-01-08 19:51 ` Rafal Luzynski
2018-01-08 23:04 ` Carlos O'Donell
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=d5a99d06-1db3-7f75-c5af-3e090cf31c3c@redhat.com \
--to=carlos@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=libc-alpha@sourceware.org \
/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).