From: Shawn Pearce <spearce@spearce.org>
To: Mike Fleetwood <mike.fleetwood@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: git fast-import / working tree status question
Date: Fri, 19 Feb 2010 15:40:47 -0800 [thread overview]
Message-ID: <ec874dac1002191540p343889d7v5f14876cf0df14c8@mail.gmail.com> (raw)
In-Reply-To: <fc5ef2e01002191520u7b50c98fo3a3defe70e31292a@mail.gmail.com>
On Fri, Feb 19, 2010 at 3:20 PM, Mike Fleetwood
<mike.fleetwood@googlemail.com> wrote:
> I am a newbie using git and I am testing conversion of a personal
> project into git using fast-import. When fast-import completes
> all the files are in the repository but the working tree is empty
> and status reports all files are delete but uncommitted. I have
> to use reset --hard HEAD to unwind the pending removal of all of
> the files. Example below.
>
> Is this normal or have I missed something?
Completely normal. fast-import is a lower level command which only
works on the object directory. Frontend tools which automate the
conversion are supposed to checkout the working tree files after the
import is complete. Or, run like you did, `git reset --hard HEAD`.
prev parent reply other threads:[~2010-02-19 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 23:20 git fast-import / working tree status question Mike Fleetwood
2010-02-19 23:40 ` Shawn Pearce [this message]
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=ec874dac1002191540p343889d7v5f14876cf0df14c8@mail.gmail.com \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=mike.fleetwood@googlemail.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).