[llvm-dev] New LLVM git repository conversion prototype
Duncan P. N. Exon Smith via llvm-dev
llvm-dev at lists.llvm.org
Thu Oct 18 09:02:36 PDT 2018
> On Oct 18, 2018, at 08:01, James Y Knight <jyknight at google.com <mailto:jyknight at google.com>> wrote:
>
> On Thu, Oct 18, 2018 at 12:22 AM Duncan P. N. Exon Smith <dexonsmith at apple.com <mailto:dexonsmith at apple.com>> wrote:
> I did a sanity check of tree hashes and found something suspicious.
>
> Background: I cloned the prototype as remote "github/llvm-git-prototype" and then added the existing Git mirror as "llvm.org/llvm <http://llvm.org/llvm>":
>
> I did a couple of tree object spot checks. At ToT the tree objects match, both giving the tree 8cf37e491e61:
>
> Great, thanks for the verification!
>
> But then I looked at r3210, and the tree objects don't match:
>
> Picking another two arbitrary revisions: the tree objects for r43210 match, but not those for r3333.
>
> Do you know what would cause the trees to diverge? Could there be a correctness issue here?
>
> Indeed! There are intentional divergences from the existing git conversion -- and from the SVN repository -- before SVN r37801. Before that revision, I've fixed up some of the history where it was screwed up due to CVS shenanigans. (r37801 was the first commit actually done in SVN) I completely neglected to mention this to you last night, sorry -- I blame lack of sleep.
>
> What you _will_ find, is that the repository now matches what was actually supposed to be in it, down through llvm release 1.4. This was achieved by moving files back to their original locations, at the appropriate points in history.
Okay, that clarifies it. It's a relatively small (and early) part of history so I'm not worried about the potential bloat from this either. Thanks for the explanation!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181018/ad4cccc6/attachment.html>
More information about the llvm-dev
mailing list