git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-fast-import question

From
Troy Telford <ttelford.groups@gmail.com>
Date
Jul 30, 2009, 00:00 UTC
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.

Previous: Shawn O. Pearce
Message 3 of 3 in “git-fast-import question”
  1. Troy TelfordJul 29, 2009
  2. Shawn O. PearceJul 29, 2009
  3. Troy TelfordJul 30, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.