This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Using the vcs_to_changelog.py script
- From: Jeff Law <law at redhat dot com>
- To: Alan Modra <amodra at gmail dot com>, Simon Marchi <simon dot marchi at polymtl dot ca>
- Cc: binutils at sourceware dot org, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Wed, 12 Feb 2020 19:29:32 -0700
- Subject: Re: Using the vcs_to_changelog.py script
- References: <fae607e5-7fec-b295-a579-7a8ea7c214da@polymtl.ca> <20200213010322.GB29647@bubble.grove.modra.org>
- Reply-to: law at redhat dot com
On Thu, 2020-02-13 at 11:33 +1030, Alan Modra wrote:
> On Wed, Feb 12, 2020 at 06:32:51PM -0500, Simon Marchi wrote:
> > For illustrative purposes, here's what the script outputs for the last bunch
> > of commits in binutils-gdb:
> >
> > http://paste.ubuntu.com/p/x38zs82Rmt/
>
> Not fit for the original purpose of change logs as far as developers
> are concerned, but I for one don't use them at all nowadays to see
> what changed when. "git log" and "git blame" are far better.
I'm in a similar position. For years ChangeLogs were my go-to for
initial archaeology, but I find myself using git log and git blame most
of the time now.
>
> Does this satisfy the FSF legal requirements? "Who changed what"
> won't be accurate unless committers remember to set the author
> properly on commits made for other people.
RMS and/or the FSF blessed it for glibc a while back. So it'd seem
suitable for other projects under the FSF umbrella. I'm hoping we'll
make the same change for GCC, but there's some inertia to push through
:(
jeff