Merge commits and ChangeLog entries (was: onwards to git)

[Thomas Schwinge <tschwinge at gnu dot org>]

Hello!

On Fri, May 15, 2009 at 11:49:18PM +0200, Jim Meyering wrote:
> E.g., I'll be installing a so-called update hook to prohibit
> pushing merge commits

Why prohibit merge commits?  Sure, for a lot of scenarios they're not of
any value, but for a number of other scenarios it is, in my opinion,
helpful to see in which context a patch was created (i.e., which revision
of the repository a patch was originally written for).


Next topic: do the glibc maintainers still want to continue maintaining
ChangeLog entries manually?  Jim already knows this, I suppose ;-), but
other people perhaps don't: GNU coreutils has a nice scheme,
<http://git.savannah.gnu.org/cgit/coreutils.git/tree/HACKING#n201>, that
allows them to automatically create ChangeLog files from Git commit
messages, and these ChangeLog files are no longer stored in the VCS, but
only created for release tarballs.  I could imagine that Jim discussed
this already before, but what were the reasons for not adopting this
easier scheme for glibc?


Regards,
 Thomas

Attachment: signature.asc
Description: Digital signature