On Thu, Sep 6, 2018, 5:49 PM Ed Maste <[email protected]> wrote: > On 4 September 2018 at 06:53, Kurt Jaeger <[email protected]> wrote: > > > > The github repo isn't official, because there are still some > > consistency issues. The consistency problem is: If an repo-copy > > from svn to git is done, how can that repo-copy be done a second > > time and still keep the same commit ids (in the git repo) ? > > Restarting a svn->git conversion from scratch will usually generate > the same commit hashes. However, there's an unfortunate point where > the svn mirroring messed up [1] that resulted in bogus metadata on the > manufactured git commit, and all hashes from that point on are broken. > (Ironically this was from a bug in the svn mirroring process, not the > svn->git conversion or git itself.) > > Assuming we're confident the issue in the svn mirroring process is > fixed and will not recur we can redo the conversion, with a one-time > change to all hashes from the offending commit on, and they would not > change again in the future. > > [1] > https://github.com/freebsd/freebsd/commit/c5e8194f33abf05314599d63c1e00d01aa354f47
What is the upgrade story for current users? How do they cut over? We need a how to or something in the handbook. Warner > > _______________________________________________ > [email protected] mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[email protected]" > _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[email protected]"
