From: Troy Telford <ttelford.groups@gmail.com>
Date: Thu, 30 Jul 2009 00:00:02 GMT
Subject: Re: git-fast-import question
Message-ID: <1e30a6d10907291700u55eef62cy22c87815602616ee@mail.gmail.com>
In-Reply-To: <20090729224855.GD1033@spearce.org>

> My initial guess is, you don't have what
> you think you have.

Thanks for the tip - you're right in that I don't have what I think I have.

Namely, there are entire sections of the dump file that aren't getting
imported.  fast-import isn't complaining about it either.

commit refs/heads/foo
<various metadata>
M 100644 :mark path/to/some/file

Isn't getting imported (to any branch, let alone refs/heads/foo)

So when the later commit wants to rename the file, it can't be found.

Digging a bit deeper, I found a few cases where I'd have something
along the lines of:

commit refs/heads/foo
mark :1
<etc, etc.>

commit refs/heads/foo
mark :2
from :1
<etc, etc>

ie. two sequential commits, to the same branch.  The first commit is
being imported; the second commit isn't being imported.  Many
subsequent commits are similarly cast aside - then for no reason I can
tell, commits start getting imported again.  I'd expect fast-import to
complain, but that doesn't seem to be happening.