This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Move ChangeLog to ChangeLog.old/ChangeLog.19


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 [1], 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.

[1] https://sourceware.org/ml/libc-alpha/2019-10/msg00223.html

On 09 Oct 2019, Florian Weimer wrote:

>We no longer maintain a manually-written ChangeLog file:
>
>  <https://sourceware.org/ml/libc-alpha/2019-09/msg00333.html>
>  <https://sourceware.org/ml/libc-alpha/2019-10/msg00131.html>
>
>Instead the release manager is expected to generate a ChangeLog-like
>file using scripts/gitlog_to_changelog.py.  For further details,
>see commit f2144b7874b23be7c7eb184ec601633ec6fa8fac ("Script to
>generate ChangeLog-like output from git log").
>---
> ChangeLog => ChangeLog.old/ChangeLog.19 | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename ChangeLog => ChangeLog.old/ChangeLog.19 (100%)
>
>diff --git a/ChangeLog b/ChangeLog.old/ChangeLog.19
>similarity index 100%
>rename from ChangeLog
>rename to ChangeLog.old/ChangeLog.19


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]