[Top][All Lists]

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

Re: Is it time to drop ChangeLogs?

From: Giuseppe Scrivano
Subject: Re: Is it time to drop ChangeLogs?
Date: Tue, 08 Mar 2016 22:59:42 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

John Wiegley <address@hidden> writes:

>>>>>> Dmitry Gutov <address@hidden> writes:
>> On 03/08/2016 10:56 PM, David Caldwell wrote:
>>> Since notes seem like a no-go, what about taking the same approach but
>>> using an empty commit to do it (`git commit --allow-empty`)? That way it
>>> gets pushed and merged between branches just like normal.
>> How would such commit indicate a relation to an existing commit? And after
>> making it, you can't easily edit the result, you can only redo it fully.
> What if we had a ADDENDUM file with the following contents:
>     <NEWLINE>
> Then we could teach vc-region-history and the ChangeLog generator to pay
> attention to it.

the git-to-changelog gnulib module already supports something similar
via --amend=FILE.

For example coreutils is keeping a list of corrections to make to the
git commit messages before the ChangeLog is generated:


reply via email to

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