From: Joseph Myers <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Rafal Luzynski <digitalfreak@lingonborough.com>,
<libc-alpha@sourceware.org>, Rical Jasan <ricaljasan@pacific.net>
Subject: Re: [PING][PATCH v12 5/6] Documentation to the above changes (bug 10871).
Date: Mon, 22 Jan 2018 16:01:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1801221531510.3588@digraph.polyomino.org.uk> (raw)
In-Reply-To: <c9a422d2-12ac-bdc5-6f69-5d41f56d942e@redhat.com>
On Sat, 20 Jan 2018, Carlos O'Donell wrote:
> We should stick to discussing release blockers:
> https://sourceware.org/glibc/wiki/Release/2.27#Release_blockers.3F
>
> All "Desirable this release" should be deferred to 2.28.
Well - we may not need to decide on RISC-V yet, as it's low risk for other
ports, but unless version 5 fully addresses all issues raised with version
4 without going back on fixes for issues with previous versions, it
doesn't look like it would make it as version 6 wouldn't be ready until
after 2.27 is out.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-01-22 16:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 8:12 [PATCH v12 0/6][BZ 10871] Month names in alternative grammatical case Rafal Luzynski
2018-01-12 8:14 ` [PATCH v12 1/6] Implement alternative month names (bug 10871) Rafal Luzynski
2018-01-22 10:36 ` [COMMITTED][PATCH " Rafal Luzynski
2018-01-22 15:51 ` Joseph Myers
2018-01-22 20:15 ` Rafal Luzynski
2018-01-12 8:16 ` [PATCH v12 3/6] Abbreviated alternative month names (%Ob) also added " Rafal Luzynski
2018-01-22 10:38 ` [COMMITTED][PATCH " Rafal Luzynski
2018-01-12 8:18 ` [PATCH v12 5/6] Documentation to the above changes " Rafal Luzynski
2018-01-15 3:42 ` Rical Jasan
2018-01-15 6:28 ` Carlos O'Donell
2018-01-15 8:31 ` Rical Jasan
2018-01-15 11:53 ` Rafal Luzynski
2018-01-15 11:47 ` Rafal Luzynski
2018-01-18 12:04 ` [PING][PATCH " Rafal Luzynski
2018-01-18 13:36 ` Joseph Myers
2018-01-20 8:44 ` Carlos O'Donell
2018-01-22 16:01 ` Joseph Myers [this message]
2018-01-20 8:36 ` [PATCH " Rical Jasan
2018-01-20 8:39 ` Carlos O'Donell
2018-01-20 10:50 ` Rafal Luzynski
2018-01-22 8:43 ` Rafal Luzynski
2018-01-23 3:41 ` Rical Jasan
2018-01-23 22:09 ` Rafal Luzynski
2018-01-25 0:45 ` Rafal Luzynski
2018-01-25 1:47 ` Carlos O'Donell
2018-01-31 17:22 ` Rafal Luzynski
2018-01-22 10:40 ` Rafal Luzynski
2018-01-12 8:20 ` [PATCH v12 6/6] pl_PL: Add alternative month names " Rafal Luzynski
2018-01-22 10:42 ` [COMMITTED][PATCH " Rafal Luzynski
2018-01-13 11:05 ` [PATCH v12 0/6][BZ 10871] Month names in alternative grammatical case Rafal Luzynski
2018-01-14 3:53 ` Carlos O'Donell
2018-01-14 15:03 ` Rafal Luzynski
2018-01-20 8:41 ` Carlos O'Donell
2018-01-20 10:47 ` Rafal Luzynski
2018-01-20 22:46 ` Carlos O'Donell
2018-02-19 10:12 ` Khem Raj
2018-02-22 0:24 ` Rafal Luzynski
2018-02-22 5:25 ` Carlos O'Donell
2018-02-22 5:58 ` Khem Raj
2018-02-22 6:52 ` 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=alpine.DEB.2.20.1801221531510.3588@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=libc-alpha@sourceware.org \
--cc=ricaljasan@pacific.net \
/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).