From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: libc-alpha@sourceware.org, "Dmitry V. Levin" <ldv@altlinux.org>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: Question: more languages to support alternative month names?
Date: Thu, 15 Mar 2018 11:30:00 -0000 [thread overview]
Message-ID: <1658876568.24456.1521113441579@poczta.nazwa.pl> (raw)
In-Reply-To: <20180314122803.GA27465@altlinux.org>
14.03.2018 13:20 Florian Weimer <fweimer@redhat.com> wrote:
> [...]
> NEWS updates for 2.27.1 should happen in the 2.27.1 section. There is
> only the bug list so far, so you should add a new section for these
> changes. Post a patch for review to libc-stable if unsure.
Thank you for the explanation about NEWS and mentioning libc-stable.
It's never hurting so it's better to post. Here it is:
https://sourceware.org/ml/libc-stable/2018-03/msg00012.html
14.03.2018 13:28 "Dmitry V. Levin" <ldv@altlinux.org> wrote:
> [...]
> You main backporting tool is "git cherry-pick -x",
> the process of cherry-picking is straightforward assuming that
> you have a working merge-changelog referenced by .gitattributes file.
>
> When a cherry-picked commit fixes a bug, the commit has to be amended
> to explicitly list this fixed bug in "Version 2.27.1" part of NEWS.
> You can look at the output of
> git log -p glibc-2.27..glibc-2.27-27-gb63daad -- NEWS
> command to get an idea how this works.
Thank you, this is exactly the information which I missed.
> If you are going to list languages supporting the genitive case of month
> names, a new section should be within "Version 2.27.1" part of NEWS, too.
Added, patches sent for a quick review to libc-stable (see the link above).
I will especially appreciate the proofreading of NEWS updates.
Best regards,
Rafal
prev parent reply other threads:[~2018-03-15 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 14:02 Rafal Luzynski
2018-02-15 22:01 ` Carlos O'Donell
2018-02-16 6:44 ` Rafal Luzynski
2018-03-14 12:10 ` Rafal Luzynski
2018-03-14 12:20 ` Florian Weimer
2018-03-14 12:28 ` Dmitry V. Levin
2018-03-15 11:30 ` Rafal Luzynski [this message]
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=1658876568.24456.1521113441579@poczta.nazwa.pl \
--to=digitalfreak@lingonborough.com \
--cc=fweimer@redhat.com \
--cc=ldv@altlinux.org \
--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).