[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: April 7 cutover for generating ChangeLog automatically

From: Paul Eggert
Subject: Re: April 7 cutover for generating ChangeLog automatically
Date: Tue, 31 Mar 2015 11:17:40 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0

On 03/31/2015 07:07 AM, Nicolas Petton wrote:
Does it mean that the ChangeLog files won't be updated anymore or that
they will be updated only from time to time (like right before a release
or something like that)?

The latter. The ChangeLog history files (ChangeLog.1, etc.) will be updated only when someone feels like updating them, either by editing them manually and committing the changes, or by running 'make change-history'. 'make change-history' will prepend copies of recent commit messages to ChangeLog.1, thus causing those commit messages to no longer be considered "recent".

There will be only one file called 'ChangeLog', at the top level. You can generate it automatically from recent commit messages by running 'make ChangeLog', but intent is that it is an output file and is not committed to the repository. (Unlike 'make change-history', 'make ChangeLog' doesn't cause the commits to be considered "recent".) 'make dist' uses 'make ChangeLog' to create the ChangeLog file that is put into the tarball.

I think that admin/make-tarball.txt will have to be updated.
Yes, that's part of the patch proposed in Bug#19113.  Please see:


I'm attaching the part that updates make-tarball.txt.

Attachment: make-tarball.diff
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]