From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: TAMUKI Shoichi <tamuki@linet.gr.jp>, libc-alpha@sourceware.org
Cc: Felix Yan <felixonmars@archlinux.org>,
Carlos O'Donell <carlos@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
Zack Weinberg <zackw@panix.com>
Subject: Re: [PATCH 1/3] NEWS: Mention Minguo calendar support added [BZ #24293]
Date: Tue, 19 Mar 2019 00:24:53 +0100 (CET) [thread overview]
Message-ID: <2129981675.41202.1552951493828@poczta.nazwa.pl> (raw)
In-Reply-To: <201903171028.AA04287@tamuki.linet.gr.jp>
17.03.2019 11:28 TAMUKI Shoichi <tamuki@linet.gr.jp> wrote:
>
> Hello Rafal-san,
>
> From: Rafal Luzynski <digitalfreak@lingonborough.com>
> Subject: [PATCH 1/3] NEWS: Mention Minguo calendar support added [BZ
> #24293]
> Date: Fri, 15 Mar 2019 12:47:48 +0100 (CET)
>
> > diff --git a/NEWS b/NEWS
> > index f12524d..a0a9ed5 100644
> > --- a/NEWS
> > +++ b/NEWS
> > @@ -18,6 +18,10 @@ Major new features:
> >
> > * On Linux, the gettid function has been added.
> >
> > +* Minguo (traditional Chinese) calendar support has been added as an
> > + alternative calendar for the following locales: cmn_TW, hak_TW,
> > lzh_TW,
> > + nan_TW, zh_TW.
> > +
> > Deprecated and removed features, and other changes affecting
> > compatibility:
> >
> > * The functions clock_gettime, clock_getres, clock_settime,
>
> Looks good to me.
Thank you. I would like to hear some feedback from more experienced
maintainers, especially those who are English native speakers and are
able to provide proofreading. CC'ing people who were helpful in the
past.
Regards,
Rafal
next prev parent reply other threads:[~2019-03-18 23:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 11:46 [PATCH 0/3] Additional changes after introducing Minguo calendar and zero-padding in %Ey Rafal Luzynski
2019-03-15 11:47 ` [PATCH 1/3] NEWS: Mention Minguo calendar support added [BZ #24293] Rafal Luzynski
2019-03-17 10:28 ` TAMUKI Shoichi
2019-03-18 23:24 ` Rafal Luzynski [this message]
2019-03-15 11:48 ` [PATCH 2/3] time/tst-strftime2.c: Make the file easier to maintain Rafal Luzynski
2019-03-17 10:32 ` TAMUKI Shoichi
2019-03-18 23:30 ` Rafal Luzynski
2019-03-20 9:19 ` TAMUKI Shoichi
2019-03-27 3:28 ` TAMUKI Shoichi
2019-03-15 11:49 ` [PATCH 3/3] time: Add tests for Minguo calendar [BZ #24293] Rafal Luzynski
2019-03-15 11:53 ` Rafal Luzynski
2019-03-17 10:35 ` TAMUKI Shoichi
2019-03-18 23:35 ` Rafal Luzynski
2019-03-20 9:21 ` TAMUKI Shoichi
2019-03-24 11:40 ` TAMUKI Shoichi
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2129981675.41202.1552951493828@poczta.nazwa.pl \
--to=digitalfreak@lingonborough.com \
--cc=carlos@redhat.com \
--cc=felixonmars@archlinux.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=tamuki@linet.gr.jp \
--cc=zackw@panix.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).