public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: <gcc@gcc.gnu.org>
Cc: <esr@thyrsus.com>
Subject: Re: Test GCC conversion with reposurgeon available
Date: Sun, 22 Dec 2019 13:57:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.21.1912221347060.32171@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.1912191624240.26566@digraph.polyomino.org.uk>

On Thu, 19 Dec 2019, Joseph Myers wrote:

> And two more.
> 
> git+ssh://gcc.gnu.org/home/gccadmin/gcc-reposurgeon-4a.git
> git+ssh://gcc.gnu.org/home/gccadmin/gcc-reposurgeon-4b.git

Two more.

git+ssh://gcc.gnu.org/home/gccadmin/gcc-reposurgeon-5a.git
git+ssh://gcc.gnu.org/home/gccadmin/gcc-reposurgeon-5b.git

The main changes are:

* The case of both svnmerge-integrated and svn:mergeinfo being set is now 
handled properly, so the commit Bernd found is interpreted as a merge from 
trunk to named-addr-spaces-branch and has exactly two parents as expected, 
with the parents corresponding to the merges from other branches to trunk 
being optimized away.

* The author map used now avoids timezone-only entries also remapping 
email addresses, so the email addresses from the ChangeLogs are used 
whenever a commit adds ChangeLog entries from exactly one author.

* When commits add ChangeLog entries from more than one author (e.g. 
merges done in CVS), the committer is now used as the author rather than 
selecting one of the authors from the ChangeLog entries.

* The latest whitelisting / PR corrections are used with Richard's script 
(430 checkme: entries remain).

* One fix to the ref renaming in gcc-reposurgeon-5b.git so that the tag 
gcc-3_2-rhl8-3_2-7 properly ends up in vendors rather than prereleases.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2019-12-22 13:57 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 [this message]
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
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.1912221347060.32171@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=esr@thyrsus.com \
    --cc=gcc@gcc.gnu.org \
    /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).