From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: Re: Tips for debugging fast-import front-ends
Date: Mon, 16 Jul 2007 15:32:31 +0200 [thread overview]
Message-ID: <469B736F.12FA24EA@eudaptics.com> (raw)
In-Reply-To: Pine.LNX.4.64.0707161336570.24955@reaper.quantumfyre.co.uk
Julian Phillips wrote:
> 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
next prev parent reply other threads:[~2007-07-16 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 12:45 Tips for debugging fast-import front-ends Julian Phillips
2007-07-16 13:32 ` Johannes Sixt [this message]
2007-07-17 3:27 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=469B736F.12FA24EA@eudaptics.com \
--to=j.sixt@eudaptics.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.