HEADS UP: FreeBSD git mirrors demoted to beta status, need your help
Alfred Perlstein
bright at mu.org
Thu Dec 20 23:26:50 UTC 2012
Ulrich,
Are you still hoping for feedback on this?
If so I am currently setting up to run your scripts from:
http://wiki.freebsd.org/GitWorkflow#History
Let me know if that is not needed though because if I don't need to then
I can save myself a bunch of work.
I'll report back to you on my success or not.
-Alfred
On 12/15/12 5:22 AM, Ulrich Spörlein wrote:
> Bad news everyone,
>
> tl;dr The git mirror of the source repository needs to be re-rolled to
> make the conversion deterministically repeatable, this will change
> pretty much all git commit hashes.
>
> The re-roll will be done January 15, 2013.
>
> Not affected are the ports and doc repositories, nor is the svn_head
> (for use with git-svn) affected.
>
>
> Background
>
> The converter (svn2git) was handing commits and objects to git's
> fast-import in arbitrary order, this makes merge commits have an
> arbitrary order of their parent commits and thus these merge commits
> have changing commit hashes for each converter run.
>
> This has been fixed, but requires us to move all the branches over to
> this deterministic scheme, which will change all their commit hashes.
> None of the contents of these commits change, so rebasing/remerging your
> work into these branches is possible without running into any merge
> conflicts.
>
>
> We need your help
>
> A goal of these conversions is to have them repeatable by you (yes,
> you!), so the correctness of the conversion can be verified. There are
> also no backups of the conversion runs, as they should be repeatable
> anyway.
>
> We need 2-3 volunteers to run these conversions themselves and verify
> that the produced commit hashes match the published ones. The necessary
> steps to do this are documented on the Wiki under
>
> http://wiki.freebsd.org/GitWorkflow#History
>
> Please send me your output of git show-ref in a private mail, thanks.
>
> Cheers,
> Uli
>
> PS: This re-roll has nothing to do with the recent security incident.
More information about the freebsd-current
mailing list