This is the mail archive of the
mailing list for the glibc project.
Re: ChangeLog entry complexity
- From: Eric Wong <normalperson at yhbt dot net>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: Petr Baudis <pasky at ucw dot cz>, Roland McGrath <roland at hack dot frob dot com>, OndÅej BÃlka <neleai at seznam dot cz>, libc-alpha at sourceware dot org
- Date: Mon, 25 Mar 2013 20:53:00 +0000
- Subject: Re: ChangeLog entry complexity
- References: <20130224085129 dot GA5898 at domone dot kolej dot mff dot cuni dot cz> <20130311132836 dot GA6016 at domone dot kolej dot mff dot cuni dot cz> <20130311162425 dot DAD282C083 at topped-with-meat dot com> <20130311174341 dot GA28265 at domone dot kolej dot mff dot cuni dot cz> <20130311174940 dot 0E0512C08D at topped-with-meat dot com> <513E4924 dot 4010500 at redhat dot com> <20130311214322 dot GC31274 at machine dot or dot cz> <20130311214635 dot 5B9D32C08F at topped-with-meat dot com> <20130325164624 dot GA6137 at machine dot or dot cz> <51508192 dot 90702 at redhat dot com>
Carlos O'Donell <email@example.com> wrote:
> Does anyone feel strongly that detailed change logs are limiting our
> acceptance of new developers to the community?
As a once-in-a-century-drive-by contributor, yes.
I strongly prefer detailed Linux kernel-style commit messages
documenting _why_, and only the "how" when it is not obvious.
As others have said, git is fast and powerful. There is no benefit to
reading a static ChangeLog when one can run git blame/log with the
appropriate options to get exactly what you need (and most importantly,
quickly filter out what one does not want).
ChangeLog entries also lead to needing extra tools like
git-merge-changelog instead of just doing a plain cherry-pick/am.
> If anything the most difficult bar if the copyright assignment,
> the rest is just work.
Copyright assignment is also a pain. Plenty of *GPL projects
get by just fine without it.