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

Re: Tips for debugging fast-import front-ends

From
Johannes Sixt <j.sixt@eudaptics.com>
Date
Jul 16, 2007, 13:32 UTC
Message-ID
<469B736F.12FA24EA@eudaptics.com>
In-Reply-To
<Pine.LNX.4.64.0707161336570.24955@reaper.quantumfyre.co.uk>
Julian Phillips wrote:
Show 10 quoted lines
> At some point in the "messy" phase I get an error from fast-import saying:
> 
> fatal: path foo not in branch
> 
> This seems to happen when I attempt to copy a file that is also changed in
> the same commit.  What I would like to do is find out what things look
> like just before that point - the problem is that fast-import seems to not
> create anything on failure.  So, apart restarting the import and stopping
> just before the broken commit, is there any way to find out what
> fast-import thinks the branch looks like?

Redirect the input stream to a file instead of to fast-import, then feed fast-import from this file. This way you can reproduce the failure more quickly. Also, you can run fast-import from a debugger.

-- Hannes
Previous: Julian PhillipsNext: Shawn O. Pearce
Message 2 of 3 in “Tips for debugging fast-import front-ends”
  1. Julian PhillipsJul 16, 2007
  2. Johannes SixtJul 16, 2007
  3. Shawn O. PearceJul 17, 2007

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.