From: Simon Marchi <simon.marchi@polymtl.ca>
To: law@redhat.com, Alan Modra <amodra@gmail.com>
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 03:13:00 -0000 [thread overview]
Message-ID: <5d79d322-d9a7-dceb-6cdb-a8e240f22fe0@polymtl.ca> (raw)
In-Reply-To: <97220aed713c824cecd34a5eceee1af3b63ebd18.camel@redhat.com>
> On Thu, 2020-02-13 at 11:33 +1030, Alan Modra wrote:
>> 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.
This naturally happens when using the typical git workflow. If someone sends
a patch using git-send-email and somebody else applies it using git-am, the
authorship information reflects the original author's identity.
We should always encourage people to send patches using git-send-email (or
worst case, git-format-patch) and not plain diffs, for this reason and many
others.
On 2020-02-12 9:29 p.m., Jeff Law wrote:
> 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
> :(
That is exactly what I presumed and what I am hoping for.
But the proposed changes to standards.texi do specifically mention that using
this script is fine (the script name changed, but I am fairly sure it's
referring to that script):
https://lists.gnu.org/archive/html/bug-standards/2020-01/msg00000.html
Simon
next prev parent reply other threads:[~2020-02-13 3:13 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
2020-02-13 3:13 ` Simon Marchi [this message]
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=5d79d322-d9a7-dceb-6cdb-a8e240f22fe0@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=law@redhat.com \
/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).