This is the mail archive of the
mailing list for the glibc project.
Re: ChangeLog entry complexity
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Eric Wong <normalperson at yhbt dot net>
- Cc: Carlos O'Donell <carlos at redhat dot com>, 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: Wed, 27 Mar 2013 14:31:37 +0000
- Subject: Re: ChangeLog entry complexity
- References: <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> <20130325205300 dot GA24293 at dcvr dot yhbt dot net> <Pine dot LNX dot 4 dot 64 dot 1303261741360 dot 8202 at digraph dot polyomino dot org dot uk> <20130327024859 dot GA25013 at dcvr dot yhbt dot net>
On Wed, 27 Mar 2013, Eric Wong wrote:
> > Given the messy state of the history converted from CVS (sometimes the
> > heuristics to combine separate CVS commits to separate files into a single
> > git commit helped, but sometimes they made things worse), in practice the
> > ChangeLogs are often a better place to find all the history in one place
> > (together with checking the old CVS repository in tricky cases).
> Old history becomes less relevant over time. Old changelogs will
> always be available if needed.
A key point is *in one place* - it's easy to grep the ChangeLogs for
references to a particular file name or function name. (I've no idea how
to get git to show all changes to a file of a given name, anywhere in the
source tree a file of that name may have appeared at any time in the past
- or to files whose names matched a given pattern - or to functions
anywhere in the source tree with a given name, or whose names matched a
given pattern. The sysdeps structure of glibc makes those natural things
to do. But supposing git does have a way to list such changes based on
patterns in file or function names, the "in one place" issue still
> git has a "notes" feature which allows supplementing commit messages.
Any idea why this isn't used by gitlog-to-changelog to find the
modifications to apply to those messages?
Joseph S. Myers