This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] Move ChangeLog to ChangeLog.old/ChangeLog.19
- From: Siddhesh Poyarekar <siddhesh at gotplt dot org>
- To: Joseph Myers <joseph at codesourcery dot com>, "Gabriel F. T. Gomes" <gabriel at inconstante dot net dot br>
- Cc: Florian Weimer <fweimer at redhat dot com>, libc-alpha at sourceware dot org
- Date: Wed, 9 Oct 2019 14:05:56 -0400
- Subject: Re: [PATCH] Move ChangeLog to ChangeLog.old/ChangeLog.19
- References: <firstname.lastname@example.org> <20191009102348.16dd1125@tereshkova> <alpine.DEB.email@example.com>
On 09/10/19 12:18 pm, Joseph Myers wrote:
> On Wed, 9 Oct 2019, Gabriel F. T. Gomes wrote:
>> I support this change and the stop of manually-written ChangeLog
>> entries when this patch lands as a commit in the repository. Taking into
>> account what Joseph raised in a different thread , I suppose that such
>> commit could be documented as the beginning of the range for automatic
>> ChangeLog generation *for this specific cycle*, where both manually and
>> automatically generated ChangeLog entries will coexist. For future
>> cycles, I don't know how to document it.
> My expectation for would be that the automatic ChangeLog generation is
> always the last one before tagging and branching (so for future cycles
> it's run for commits from the last release tag up to HEAD at that point,
> whereas for this cycle the starting commit would be the point at which we
> renamed the manually written ChangeLog, not the previous release tag).
I think I understand your position now, thank you for explaining it. I
will generate the ChangeLog from Florian's commit up to latest HEAD as
part of the release process, commit it and then tag glibc-2.31.