From: "Shawn O. Pearce" <spearce@spearce.org>
To: Troy Telford <ttelford.groups@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: git-fast-import question
Date: Wed, 29 Jul 2009 15:48:55 -0700 [thread overview]
Message-ID: <20090729224855.GD1033@spearce.org> (raw)
In-Reply-To: <1e30a6d10907291536y3ec68caq8788aef2b7c34a6f@mail.gmail.com>
Troy Telford <ttelford.groups@gmail.com> wrote:
> But when I run fast-import, I receive an error to the extent of:
> fatal: Path path/to/some/file not in branch
>
> So to me, it looks like the file that I'm renaming should exist in the
> branch - it's not being renamed anywhere, not being deleted, and the
> branch isn't reset. Yet fast-import doesn't seem to think the file
> exists.
Perhaps try inserting a checkpoint just before the rename commit,
so you can actually look at the tree structure in the output branch
when the crash occurs. My initial guess is, you don't have what
you think you have.
--
Shawn.
next prev parent reply other threads:[~2009-07-29 22:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 22:36 git-fast-import question Troy Telford
2009-07-29 22:48 ` Shawn O. Pearce [this message]
2009-07-30 0:00 ` Troy Telford
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=20090729224855.GD1033@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=ttelford.groups@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).