From: Carlos O'Donell <carlos@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Rafal Luzynski <digitalfreak@lingonborough.com>,
libc-stable@sourceware.org
Subject: Re: [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963.
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <6d20b660-91e2-3777-b1f2-58081c7399fc@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1803151800430.26519@digraph.polyomino.org.uk>
On 03/15/2018 12:03 PM, Joseph Myers wrote:
> On Thu, 15 Mar 2018, Carlos O'Donell wrote:
>
>>> + [22848] ca_ES: update date definitions from CLDR
>>
>> Not marked fixed in 2.28 (target milestone should be set to 2.28 and
>> marked fixed).
>
> And people don't seem to be doing a very good job of making the NEWS
> entries on release branches for fixed bugs look like those on master
> (which include the name of the component).
All I care about is that the bug is listed, though I agree we could do
a better job.
> I advise the approach of using "scripts/list-fixed-bugs.py 2.28" to get
> the properly formatted entry to add to NEWS on the release branch. That
> does of course require you first to have properly marked the bug as fixed
> with target milestone set.
I could alter the use of the keyword glibc_X.Y to mean "Fixed on branch"
and then alter list-fixed-bugs.py X.Y to search for:
* milestone is X.Y (Bugs fixed in that release, including release branch)
* keywords includes glibc_X.Y (Bugs fixed on the release branch)
This way we avoid the needless creation of new bugs for fixing things
on release branches.
Thoughts?
c.
next prev parent reply other threads:[~2018-03-15 18:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 [PATCH 0/5] Backport of fixes " Rafal Luzynski
2018-01-01 0:00 ` [PATCH 4/5] cs_CZ locale: Add alternative month names (bug 22963) Rafal Luzynski
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Rafal Luzynski
2018-01-01 0:00 ` [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963 Rafal Luzynski
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Rafal Luzynski
2018-01-01 0:00 ` Rafal Luzynski
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Joseph Myers
2018-01-01 0:00 ` Joseph Myers
2018-01-01 0:00 ` Carlos O'Donell [this message]
2018-01-01 0:00 ` Joseph Myers
2018-01-01 0:00 ` [PATCH v2 5/5][COMMITTED] " Rafal Luzynski
2018-01-01 0:00 ` [PATCH 2/5] lt_LT locale: Update abbreviated month names (bug 22932) Rafal Luzynski
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Rafal Luzynski
2018-01-01 0:00 ` [PATCH 1/5] ca_ES locale: Update LC_TIME (bug 22848) Rafal Luzynski
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Rafal Luzynski
2018-01-01 0:00 ` [PATCH 3/5] Greek (el_CY, el_GR) locales: Introduce ab_alt_mon (bug 22937) Rafal Luzynski
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Rafal Luzynski
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=6d20b660-91e2-3777-b1f2-58081c7399fc@redhat.com \
--to=carlos@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=joseph@codesourcery.com \
--cc=libc-stable@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).