From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: libc-alpha@sourceware.org
Subject: [RFC][PATCH v4 00/11][BZ 10871] Month names in genitive case
Date: Fri, 28 Oct 2016 00:40:00 -0000 [thread overview]
Message-ID: <1785621073.1799944.1477615241237@poczta.nazwa.pl> (raw)
This is the third version of my attempt to fix the bug 10871. [1]
The first version has been sent to this list in January, [2] the
second version has been sent in March, [3] the third version has
been sent on October 18 [4].
The main difference between the previous set of patches and this
new one is that this new one also implements the backward
compatibility for __nl_langinfo_l(), [5] __strftime_l(), and
__wcsftime_l(). [6]
This set of patches deliberately skips some patches which have
not been changed since the previous version. I hope this avoids
some noise.
Here is a short description of the following patches:
1. Add the alternative month names support to nl_langinfo(3) (the
ALTMON_... constants.) This new patch does not change
conform/data/langinfo.h-data, as requested in [7].
2. Provide backward compatibility for nl_langinfo(),
nl_langinfo_l(), and also __nl_langinfo_l(), as requested in [5].
3. Rebuild abilists to reflect nl_langinfo(), nl_langinfo_l(),
and __nl_langinfo_l() changes - generated automatically, also rebased.
4. Deliberately skipped because not changed, you can find it here:
https://sourceware.org/ml/libc-alpha/2016-10/msg00281.html
5. Deliberately skipped because not changed, you can find it here:
https://sourceware.org/ml/libc-alpha/2016-10/msg00282.html
6. Provide backward compatibility for strftime(), strftime_l(),
wcsftime(), wcsftime_l(), and also __strftime_l() and __wcsftime_l(),
as requested in [6].
7. Rebuild abilists to reflect the changes in strftime(), strftime_l(),
wcsftime(), wcsftime_l(), and also __strftime_l() and __wcsftime_l()
- generated automatically, also rebased.
8-11. Deliberately skipped because not changed, you can find them:
https://sourceware.org/ml/libc-alpha/2016-10/msg00285.html
https://sourceware.org/ml/libc-alpha/2016-10/msg00286.html
https://sourceware.org/ml/libc-alpha/2016-10/msg00287.html
https://sourceware.org/ml/libc-alpha/2016-10/msg00288.html
I'll appreciate your reviews and comments.
Best regards,
Rafal Luzynski
[1] https://sourceware.org/bugzilla/show_bug.cgi?id=10871
[2] https://sourceware.org/ml/libc-alpha/2016-01/msg00143.html
[3] https://sourceware.org/ml/libc-alpha/2016-03/msg00616.html
[4] https://sourceware.org/ml/libc-alpha/2016-10/msg00277.html
[5] https://sourceware.org/bugzilla/show_bug.cgi?id=10871#c58
[6] https://sourceware.org/ml/libc-alpha/2016-10/msg00304.html
[7] https://sourceware.org/ml/libc-alpha/2016-10/msg00303.html
reply other threads:[~2016-10-28 0:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1785621073.1799944.1477615241237@poczta.nazwa.pl \
--to=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).