From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: libc-alpha@sourceware.org
Cc: Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH v11 1/5] Implement alternative month names (bug 10871).
Date: Tue, 09 Jan 2018 00:14:00 -0000 [thread overview]
Message-ID: <1272641264.675250.1515456885261@poczta.nazwa.pl> (raw)
In-Reply-To: <309950992.675174.1515455961934@poczta.nazwa.pl>
9.01.2018 00:59 Rafal Luzynski <digitalfreak@lingonborough.com> wrote:
> [...]
> [BZ #10871]
> * locale/C-time.c: Add alternative month names, define them as the
> same as mon explicitly.
> * locale/categories.def: alt_mon and wide-alt_mon added.
> * locale/langinfo.h [__USE_GNU]: New public symbols ALTMON_1,
> ALTMON_2, ALTMON_3, ALTMON_4, ALTMON_5, ALTMON_6, ALTMON_7,
> ALTMON_8, ALTMON_9, ALTMON_10, ALTMON_11, ALTMON_12,
> _NL_WALTMON_1, _NL_WALTMON_2, _NL_WALTMON_3, _NL_WALTMON_4,
> _NL_WALTMON_5, _NL_WALTMON_6, _NL_WALTMON_7, _NL_WALTMON_8,
> _NL_WALTMON_9, _NL_WALTMON_10, _NL_WALTMON_11, _NL_WALTMON_12.
Carlos, what do you think about splitting this into:
* locale/langinfo.h: New public symbols _NL_WALTMON_1,
_NL_WALTMON_2, _NL_WALTMON_3, _NL_WALTMON_4, _NL_WALTMON_5,
_NL_WALTMON_6, _NL_WALTMON_7, _NL_WALTMON_8, _NL_WALTMON_9,
_NL_WALTMON_10, _NL_WALTMON_11, _NL_WALTMON_12.
[__USE_GNU]: New public symbols ALTMON_1, ALTMON_2, ALTMON_3,
ALTMON_4, ALTMON_5, ALTMON_6, ALTMON_7, ALTMON_8, ALTMON_9,
ALTMON_10, ALTMON_11, ALTMON_12.
or even:
* locale/langinfo.h: New public symbols __ALTMON_1,
__ALTMON_2, __ALTMON_3, __ALTMON_4, __ALTMON_5, __ALTMON_6,
__ALTMON_7, __ALTMON_8, __ALTMON_9, __ALTMON_10, __ALTMON_11,
__ALTMON_12, _NL_WALTMON_1, _NL_WALTMON_2, _NL_WALTMON_3,
_NL_WALTMON_4, _NL_WALTMON_5, _NL_WALTMON_6, _NL_WALTMON_7,
_NL_WALTMON_8, _NL_WALTMON_9, _NL_WALTMON_10, _NL_WALTMON_11,
_NL_WALTMON_12.
[__USE_GNU]: New public symbols ALTMON_1, ALTMON_2, ALTMON_3,
ALTMON_4, ALTMON_5, ALTMON_6, ALTMON_7, ALTMON_8, ALTMON_9,
ALTMON_10, ALTMON_11, ALTMON_12.
?
Regards,
Rafal
next prev parent reply other threads:[~2018-01-09 0:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 23:54 [PATCH v11 0/5][BZ 10871] Month names in alternative grammatical case Rafal Luzynski
2018-01-08 23:59 ` [PATCH v11 1/5] Implement alternative month names (bug 10871) Rafal Luzynski
2018-01-09 0:14 ` Rafal Luzynski [this message]
2018-01-11 4:20 ` Carlos O'Donell
2018-01-11 2:16 ` Dmitry V. Levin
2018-01-11 5:05 ` Carlos O'Donell
2018-01-12 3:44 ` Rafal Luzynski
2018-01-12 4:09 ` Carlos O'Donell
2018-01-11 11:46 ` Rafal Luzynski
2018-01-11 12:25 ` Dmitry V. Levin
2018-01-11 14:32 ` Zack Weinberg
2018-01-11 15:07 ` Dmitry V. Levin
2018-01-11 15:22 ` Zack Weinberg
2018-01-11 15:44 ` Rafal Luzynski
2018-01-11 22:26 ` Rafal Luzynski
2018-01-09 0:01 ` [PATCH v11 3/5] Abbreviated alternative month names (%Ob) also added " Rafal Luzynski
2018-01-11 5:05 ` Carlos O'Donell
2018-01-11 19:04 ` Rafal Luzynski
2018-01-11 19:14 ` Carlos O'Donell
2018-01-12 4:01 ` Rafal Luzynski
2018-01-09 0:03 ` [PATCH v11 5/5] Documentation to the above changes " Rafal Luzynski
2018-01-11 4:50 ` Carlos O'Donell
2018-01-12 4:21 ` Rafal Luzynski
2018-01-09 0:05 ` [PATCH] pl_PL: Add alternative month names " Rafal Luzynski
2018-01-09 0:20 ` Rafal Luzynski
2018-01-11 4:40 ` 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=1272641264.675250.1515456885261@poczta.nazwa.pl \
--to=digitalfreak@lingonborough.com \
--cc=carlos@redhat.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).