Re: [setup] Makefile.am patches

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Feb 15 17:36, Achim Gratz wrote:
> Corinna Vinschen writes:
> > We're not going to skip writing ChangeLog entries.  If there is some
> > automatism to write *correctly formatted* ChangeLog entries from the git
> > commit message, then that method can and should be used.
> 
> If they're correctly formatted to begin with it's no problem at all and
> the extraction into an actual ChangeLog file is easily scriptable.

I saw some .gitattributes file mentioning exactly this ChangeLog merging
in the binutils-gdb repo and copied it over so it's part of our repo as
well.

I don't know exactly where to go from there.  The comment claims the
user has to install the git-merge-changelog package and per the comment
"this is the tricky part!".  Why that's the tricky part beats me.  The
git-merge-changelog package is part of the Fedora distro.

So, is that really all there is?  Installing git-merge-changelog,
adding

  [merge "merge-changelog"]
	  name = GNU-style ChangeLog merge driver
	  driver = git-merge-changelog %O %A %B

to my .gitconfig and shoot?  So ultimately the user has to make the choice
whether generating ChangeLogs automatically or manually, right?

> > Still, how's that better than creating the automatic version number from
> > ChangeLog?
> 
> For starters it only needs to trace back to the latest tag and not
> through all commits and the tags give you an easy way to refer to
> exactly the commit some release has been made from.

Ok, I trust you tested it?  Please check in (with ChangeLog ;))


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: pgpkdOoDu3a4J.pgp
Description: PGP signature