public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
Cc: Joseph Myers <jsm@polyomino.org.uk>, gcc@gcc.gnu.org
Subject: Re: Git conversion: fixing email addresses from ChangeLog files
Date: Sat, 28 Dec 2019 20:11:00 -0000	[thread overview]
Message-ID: <20191228201115.GY4505@gate.crashing.org> (raw)
In-Reply-To: <34143dd0-3abb-c15d-db82-fd22356f20c3@arm.com>

On Sat, Dec 28, 2019 at 04:34:20PM +0000, Richard Earnshaw (lists) wrote:
> On 28/12/2019 14:54, Segher Boessenkool wrote:
> > On Sat, Dec 28, 2019 at 01:05:13PM +0000, Joseph Myers wrote:
> >> On Sat, 28 Dec 2019, Segher Boessenkool wrote:
> >>
> >>> On Fri, Dec 27, 2019 at 07:47:02PM +0000, Richard Earnshaw (lists) wrote:
> >>>>       1 Author: Segher Boessenkool <segher@kernel,crashing.org>
> >>>> *    730 Author: Segher Boessenkool <segher@kernel.crashing.org>
> >>>>       2 Author: Segher Boesssenkool <segher@kernel.crashing.org>
> >>>
> >>> The first and third are only in changelogs.  The second even happened
> >>> only once, afaics?
> >>>
> >>> These errors only happen in the reposurgeon conversion.
> >>
> >> This is about extracting attributions from changelogs when unambiguous 
> >> there, and then correcting mistakes or otherwise making minor variants 
> >> more uniform.
> > 
> > Yes, and I'm saying you probably shouldn't do that.
> 
> Why, for heavens sake?  Even Maxim's conversion is doing this.

No, it doesn't.  If people sometimes mispel their own name in a changelog
it does not put that mispeling as Author: in the git commit.

> > Note that these errors did not exist in the changelog in the commit
> > message, for example.
> 
> Yes, they did.  Or at least, they did at the time of the original commit.

No, they never did.  I always cut off the date/name/email line from the
changelog in the commit message.

> > Since people very often typo their own name (as the evidence shows), the
> > heuristic for deriving it should be robust against that.
> 
> And the statistics show that it's not hard to identify the odd cases and
> fix them up.  Only committers with just a single commits are really hard
> to spot since we don't have data to compare against other entries.

Sure, so do that?  :-)


Segher

  reply	other threads:[~2019-12-28 20:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 19:47 Richard Earnshaw (lists)
2019-12-28 11:37 ` Segher Boessenkool
2019-12-28 13:05   ` Joseph Myers
2019-12-28 14:54     ` Segher Boessenkool
2019-12-28 16:34       ` Richard Earnshaw (lists)
2019-12-28 20:11         ` Segher Boessenkool [this message]
2019-12-28 23:09           ` Richard Earnshaw (lists)
2019-12-28 16:36       ` Joseph Myers
2019-12-28 12:04 ` Jakub Jelinek
2019-12-28 16:55   ` Richard Earnshaw (lists)
2019-12-28 17:14     ` Joseph Myers
2019-12-28 17:23       ` Richard Earnshaw (lists)
2019-12-28 17:34         ` Joseph Myers
2019-12-28 18:54           ` Joseph Myers
2019-12-28 19:18             ` Eric S. Raymond
2019-12-29 17:44             ` Joseph Myers
2019-12-29 22:52               ` Joseph Myers
2019-12-28 18:37     ` Andreas Schwab
2019-12-28 23:20 ` Richard Earnshaw (lists)
2019-12-29 12:32   ` Eric S. Raymond
2019-12-29 16:25     ` Richard Earnshaw (lists)
2019-12-29 22:25       ` Eric S. Raymond
2019-12-29 22:31         ` Richard Earnshaw (lists)
2019-12-29 22:56           ` Eric S. Raymond
2019-12-30 15:38             ` Richard Earnshaw (lists)
2019-12-29 17:22     ` Jeff Law

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=20191228201115.GY4505@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jsm@polyomino.org.uk \
    /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).