This is the mail archive of the
mailing list for the GCC project.
Re: [Contrib PATCH] Add scripts to convert GCC repo from SVN to Git
- From: Maxim Kuvyrkov <maxim dot kuvyrkov at linaro dot org>
- To: Maxim Kuvyrkov <maxim dot kuvyrkov at linaro dot org>
- Cc: Jason Merrill <jason at redhat dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>, Paolo Bonzini <pbonzini at redhat dot com>
- Date: Tue, 6 Aug 2019 12:32:36 +0300
- Subject: Re: [Contrib PATCH] Add scripts to convert GCC repo from SVN to Git
- References: <E8A06A10-5BBC-4C2F-9C09-D5413B98D2DC@linaro.org> <8C62F814-2F57-4D1A-B66F-5C5ACFF37D6C@linaro.org> <4E46E435-F95C-46AD-87F0-8220D2BF4CD4@linaro.org> <CADzB+2nTUSH+i-XzAavnL3BfZjXLm53d0e3JgPfKZi5X8ijA9g@mail.gmail.com> <BC4A0163-3A45-4C3D-AA79-5DCEB6BF524A@linaro.org> <7FA7C370-04F5-448E-95D2-426607B99CF4@linaro.org> <CADzB+2=B=Fv34nqt+D103YCQocBTsVs80CCNFHkv_4cJ0gKfWQ@mail.gmail.com> <846D2EF4-879F-4518-ABA5-7DD74E6B4F18@linaro.org> <C320B2E1-09C8-46EC-8AB6-AC044BB03BA9@linaro.org>
> On Aug 5, 2019, at 11:24 AM, Maxim Kuvyrkov <email@example.com> wrote:
>> On Aug 2, 2019, at 11:41 AM, Maxim Kuvyrkov <firstname.lastname@example.org> wrote:
>>> On Aug 1, 2019, at 11:43 PM, Jason Merrill <email@example.com> wrote:
>>>> Unfortunately, current mirror does not and could not account for rewrites of SVN commit log messages. For trunk the histories of diverge in 2008 due to commit message change of r138154. This is not a single occurrence; I've compared histories only of trunk and gcc-6-branch, and both had commit message change (for gcc-6-branch see r259978).
>>>> It's up to the community is to weigh pros and cons of re-using existing GCC mirror as conversion base vs regenerating history from scratch:
>>>> Pros of using GCC mirror:
>>>> + No need to rebase public git-only branches
>>>> + No need to rebase private branches
>>>> + No need to rebase current clones, checkouts, work-in-progress trees
>>>> Cons of using GCC mirror:
>>>> - Poor author / committer IDs (this breaks patch statistics software)
>>>> - Several commit messages will not be the current "fixed" version
>>> I'm still inclined to stick with the mirror. I would expect patch
>>> statistics software to be able to be taught about multiple addresses
>>> for the same person.
>> Patch tracking software breaks on emails like <fxcoudert@138bc75d-0d04-0410-961f-82ee72b054a4> , where 38bc75d-0d04-0410-961f-82ee72b054a4 is not a reasonable domain name.
>> For completeness, I'll generate and upload a repo based on current mirror with all branches and tags converted.
> Yeah, this didn't worked as well as I hoped. Current gcc git mirror has wrong history for branches that followed scenario:
> 1. create $branch from $base at revision N
> 2. commit WORK on $branch
> 3. delete $branch
> 4. create $branch from $base at revision N+M
> 5. rebase WORK on current $branch
> Current mirror connects histories of two versions of $branch, and we get wrong history. In step (4) instead of plain history of $base we get a commit merging histories of $branch just before deletion and $base at revision N+M.
> There are many branches like this, e.g., branches/gccgo.
I've setup uploads and updates of fully converted GCC history (all branches and all tags) in 3 flavors. These will be updated roughly hourly.
This is a fresh conversion from scratch with "pretty" authors.
This is a close match to current GCC mirror. Trunk and gcc-*-branch branches are imported from the mirror, and the rest is reconstructed starting from the imported branches.
This is a fresh conversion from scratch with no author rewrites.