From: Jeff Law <law@redhat.com>
To: Alan Modra <amodra@gmail.com>, Simon Marchi <simon.marchi@polymtl.ca>
Cc: binutils@sourceware.org,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Using the vcs_to_changelog.py script
Date: Thu, 13 Feb 2020 02:29:00 -0000 [thread overview]
Message-ID: <97220aed713c824cecd34a5eceee1af3b63ebd18.camel@redhat.com> (raw)
In-Reply-To: <20200213010322.GB29647@bubble.grove.modra.org>
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
next prev parent reply other threads:[~2020-02-13 2:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 23:33 Simon Marchi
2020-02-13 1:03 ` Alan Modra
2020-02-13 2:29 ` Jeff Law [this message]
2020-02-13 3:13 ` Simon Marchi
2020-02-13 14:13 ` Eli Zaretskii
2020-02-13 3:37 ` Eli Zaretskii
2020-02-13 14:19 ` Simon Marchi
2020-02-13 15:42 ` Eli Zaretskii
2020-02-13 16:26 ` Simon Marchi
2020-02-13 18:58 ` Eli Zaretskii
2020-02-13 19:09 ` Philippe Waroquiers
2020-02-13 19:29 ` Eli Zaretskii
2020-02-13 20:56 ` Simon Marchi
2020-02-13 21:07 ` Simon Marchi
2020-02-14 9:45 ` Eli Zaretskii
2020-02-14 19:31 ` Simon Marchi
2020-02-14 20:16 ` Eli Zaretskii
2020-02-14 21:08 ` Simon Marchi
2020-02-15 7:26 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97220aed713c824cecd34a5eceee1af3b63ebd18.camel@redhat.com \
--to=law@redhat.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).