This is the mail archive of the newlib@sourceware.org mailing list for the newlib 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: [HEADSUP] Giving ChangeLog a rest

From: Eric Blake <eblake at redhat dot com>
To: Sebastian Huber <sebastian dot huber at embedded-brains dot de>, newlib at sourceware dot org
Date: Fri, 6 Nov 2015 08:43:21 -0700
Subject: Re: [HEADSUP] Giving ChangeLog a rest
Authentication-results: sourceware.org; auth=none
Openpgp: url=http://people.redhat.com/eblake/eblake.gpg
References: <20151105122655 dot GA30517 at calimero dot vinschen dot de> <563CB585 dot 1070308 at embedded-brains dot de>

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

Attachment: signature.asc
Description: OpenPGP digital signature

References:
- [HEADSUP] Giving ChangeLog a rest
  - From: Corinna Vinschen
- Re: [HEADSUP] Giving ChangeLog a rest
  - From: Sebastian Huber

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