public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <jsm@polyomino.org.uk>
To: Roman Zhuykov <zhroma@ispras.ru>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	gcc@gcc.gnu.org,     Alexander Monakov <amonakov@ispras.ru>,
	    Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
	esr@thyrsus.com,     Richard.Earnshaw@arm.com,
	rearnsha@gmail.com
Subject: Re: Test GCC conversion with reposurgeon available
Date: Wed, 25 Dec 2019 11:20:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.21.1912251110160.16462@digraph.polyomino.org.uk> (raw)
In-Reply-To: <279bf8dd-8725-c3fa-0def-130b3d128509@ispras.ru>

On Wed, 25 Dec 2019, Roman Zhuykov wrote:

> 2) Some thoughts about script for summarizing commit log messages:
> 2a) Why r143753 and r150680 not have "re PR..." summary instead of "[multiple
> changes]" ?
> 2b) On the contrary r155892 have to mention two PRs, even "[multiple changes]"
> is better here, IMHO.
> 2c) In r130050 and r155902 we have "Rename too ... " in summary, not sure how
> to make it better.
> 2d) r146882 can have better summary if we somehow organize ChangeLog priority
> (gcc/ChangeLog is more important that testsuite one).

Richard is best placed to comment on these.  His script can provide a 
complete new summary line if the automatically-generated one seems bad.

> 3a) In r155892, r155893 and r259314 Alex is not counted as the only author
> without any reason.

The first two look like cases where the only difference is in the number 
of spaces between name and email in the attributions in different 
ChangeLog files.  Should be straightforward to fix by doing more parsing / 
normalization before deciding whether attributions are the same.

The third is a case where the heuristic is applied that if a commit only 
changes ChangeLog files and nothing else, attributions should not be 
extracted from those ChangeLog files because it's particularly likely in 
that case the someone else's ChangeLog entries may be being edited.

> 3b) In r139854, r141108 and r196252 script selected the author successfully,
> while actually there are more that one.

These are all cases covered by the request-for-enhancement issue for 
adding Co-Authored-by: when the ChangeLog header names multiple authors, 
as the corresponding de facto git idiom for that case.

> 3e) r155891, r207422, r183627 and r234218 are examples of commits which don't
> touch any ChangeLog files for different reasons. Seems unsolvable in current
> approach.

If a ChangeLog file isn't touched, indeed we don't have a good basis for 
using an author identity other than the committer identity (especially 
given that some people used multiple email addresses simultaneously, with 
different ones used for different kinds of commits, and objected to having 
one with the wrong affiliation associated with a commit they made in 
connection with a different affiliation).

-- 
Joseph S. Myers
jsm@polyomino.org.uk

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

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17 21:32 Joseph Myers
2019-12-17 23:33 ` Bernd Schmidt
2019-12-18  0:51   ` Eric S. Raymond
2019-12-18  0:52   ` Joseph Myers
2019-12-18  3:28     ` Joseph Myers
2019-12-18 14:36       ` Joseph Myers
2019-12-18 13:10 ` Jason Merrill
2019-12-18 18:16   ` Joseph Myers
2019-12-19  5:50     ` Jason Merrill
2019-12-19 15:55       ` Joseph Myers
2019-12-18 21:55 ` Joseph Myers
2019-12-19  0:36   ` Bernd Schmidt
2019-12-19  0:58     ` Joseph Myers
2019-12-19 13:51   ` Test GCC conversions (publicly) available Mark Wielaard
2019-12-19 14:06     ` Eric S. Raymond
2019-12-19 14:40       ` Joseph Myers
2019-12-19 16:00         ` Eric S. Raymond
2019-12-19 16:03           ` Richard Earnshaw (lists)
2019-12-19 16:08             ` Eric S. Raymond
2019-12-19 16:29   ` Test GCC conversion with reposurgeon available Joseph Myers
2019-12-22 13:57     ` Joseph Myers
2019-12-23 17:27       ` Roman Zhuykov
2019-12-24 11:50         ` Joseph Myers
2019-12-24 15:55           ` Segher Boessenkool
2019-12-24 17:17             ` Joseph Myers
2019-12-24 18:14               ` Segher Boessenkool
2019-12-25 11:03                 ` Roman Zhuykov
2019-12-25 11:20                   ` Joseph Myers [this message]
2019-12-25 12:23                     ` Eric S. Raymond
2019-12-25 14:32                   ` Andreas Schwab
2019-12-25 14:41                     ` Joseph Myers
2019-12-25 15:10                       ` Andreas Schwab
2019-12-25 15:36                         ` Joseph Myers
2019-12-25 17:15                           ` Segher Boessenkool
2019-12-25 19:33                             ` Eric S. Raymond
2019-12-26 21:03                               ` Vincent Lefevre
2019-12-26 21:31                                 ` Eric S. Raymond
2019-12-26 22:25                                   ` Toon Moene
2019-12-26 22:32                                     ` Eric S. Raymond
2019-12-27 14:40                                       ` Segher Boessenkool
2019-12-26 22:57                                   ` Vincent Lefevre
2019-12-26 23:38                                     ` Eric S. Raymond
2019-12-25 19:40                           ` Eric S. Raymond
2019-12-27 21:29                           ` Andreas Schwab
2019-12-27 21:43                             ` Joseph Myers
2019-12-25 19:19                     ` Eric S. Raymond
2019-12-27 21:30                       ` Andreas Schwab
2019-12-28  2:43                         ` Eric S. Raymond
2019-12-27 14:37                   ` Richard Earnshaw
2019-12-24 10:57       ` Maxim Kuvyrkov
2019-12-28 16:30       ` Joseph Myers
2020-01-03 12:38         ` Joseph Myers
2020-01-06 23:58           ` Andrew Pinski
2020-01-07  0:30             ` Joseph Myers
2020-01-07  0:44             ` Richard Earnshaw
2020-01-09 12:22           ` Joseph Myers
2020-01-09 21:57             ` Joseph Myers
2020-01-09  9:44 ` GIT conversion: question about tags & release branches Martin Liška
2020-01-09 10:51   ` Richard Earnshaw (lists)
2020-01-09 11:06     ` Martin Liška
2020-01-09 11:31       ` Eric S. Raymond
2020-01-09 11:46   ` Martin Jambor
2020-01-09 11:50     ` Martin Liška
2020-01-09 12:37       ` Joseph Myers
2020-01-09 13:38         ` Martin Liška
2020-01-09 11:57     ` Richard Earnshaw (lists)
2020-01-09 11:59       ` Richard Earnshaw (lists)
2020-01-06 22:09 Test GCC conversion with reposurgeon available Loren James Rittle
2020-01-07  9:35 ` Richard Earnshaw (lists)
2020-01-07 15:53   ` Loren James Rittle

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=alpine.DEB.2.21.1912251110160.16462@digraph.polyomino.org.uk \
    --to=jsm@polyomino.org.uk \
    --cc=Richard.Earnshaw@arm.com \
    --cc=amonakov@ispras.ru \
    --cc=esr@thyrsus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=maxim.kuvyrkov@linaro.org \
    --cc=rearnsha@gmail.com \
    --cc=segher@kernel.crashing.org \
    --cc=zhroma@ispras.ru \
    /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).