[HEADSUP] Giving ChangeLog a rest

Eric Blake eblake@redhat.com
Fri Nov 6 15:49:00 GMT 2015

On 11/06/2015 07:13 AM, Sebastian Huber wrote:
> On 05/11/15 13:26, Corinna Vinschen wrote:
>> The ChangeLog file will be renamed to ChangeLog.old and no new ChangeLog
>> file will be created.
> In case you want to keep the ChangeLog format in the commit message,
> then it may make sense to add the contents of the ChangeLog file to the
> commit message that renames this file to ChangeLog.old so that you can
> search throughout in git log.

No. A multi-megabyte commit message repeating the contents of history
buys us nothing. It should be obvious enough when trawling through git
history whether the commit comes from after the cutoff (the message was
nice) or predates the cutoff (in which case the single change to
ChangeLog in that or the adjacent commits is easy to find).

Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 604 bytes
Desc: OpenPGP digital signature
URL: <http://sourceware.org/pipermail/newlib/attachments/20151106/53368468/attachment.sig>

More information about the Newlib mailing list