From: Troy Telford <ttelford.groups@gmail.com>
To: git <git@vger.kernel.org>
Subject: git-fast-import question
Date: Wed, 29 Jul 2009 16:36:33 -0600 [thread overview]
Message-ID: <1e30a6d10907291536y3ec68caq8788aef2b7c34a6f@mail.gmail.com> (raw)
I've been writing an importer from an older SCM into git. I'm getting
the following behavior with using git-fast-import:
The file I'm importing has something along the lines of:
commit refs/heads/foo
<various metadata>
M 100644 :mark path/to/some/file
Then, later on, there's another commit:
commit refs/heads/foo
<various metadata>
R path/to/some/file new/path/to/some/file
As far as I've been able to see, the :from tag points to the correct
commit (which is also in the correct branch). There are no instances
of 'reset <branch>' being called anywhere. The file isn't deleted
anywhere.
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.
I'm using git 1.6.3.3
next reply other threads:[~2009-07-29 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 22:36 Troy Telford [this message]
2009-07-29 22:48 ` git-fast-import question Shawn O. Pearce
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=1e30a6d10907291536y3ec68caq8788aef2b7c34a6f@mail.gmail.com \
--to=ttelford.groups@gmail.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 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).