Date: Thu, 6 Sep 2018 19:47:11 -0400 From: Ed Maste <emaste@freebsd.org> To: FreeBSD Current <freebsd-current@freebsd.org> Cc: tech-lists <tech-lists@zyxst.net>, Kurt Jaeger <pi@freebsd.org> Subject: Re: github freebsd and svn freebsd Message-ID: <CAPyFy2AvH5p8Oh5TBfAUJ5z6jm9GdqS252rN1ETnYa=xb4-qmg@mail.gmail.com> In-Reply-To: <20180904105302.GD2118@home.opsec.eu> References: <18a5abcc-afbc-41c3-75ed-e33607e70c8f@zyxst.net> <20180904105302.GD2118@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 September 2018 at 06:53, Kurt Jaeger <pi@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2AvH5p8Oh5TBfAUJ5z6jm9GdqS252rN1ETnYa=xb4-qmg>