From: Steven Walter <stevenrwalter@gmail.com>
To: Jing Xue <jingxue@digizenstudio.com>
Cc: git@vger.kernel.org
Subject: Re: git-svnimport: what to do after -i?
Date: Wed, 22 Aug 2007 12:58:47 -0400 [thread overview]
Message-ID: <20070822165846.GA17815@dervierte> (raw)
In-Reply-To: <20070822113325.1bihryuk4gko8kgs@intranet.digizenstudio.com>
On Wed, Aug 22, 2007 at 11:33:25AM -0400, Jing Xue wrote:
>
> I am new to git. Last night I used "git svnimport -i" to import a svn
> project. It finished successfully. The only problem now is I can't
> seem to be able to checkout a working copy. In other words, I have a
> 'projectFoo' directory, with only .git in it, but not any actual
> working files. "git-branch" shows two branches, master and origin.
> "git-checkout master" returns successfully, but does nothing.
>
> I guess that's because I used -i without fully understanding what it
> implies. Is there any way to checkout a working directory?
>
> Thanks in advance for any ideas.
> --
> Jing Xue
See if "git reset --hard master" doesn't check out the files for you. I
seem to recall an issue where, after an import, no files were checked
out. reset fixed it for me.
--
-Steven Walter <stevenrwalter@gmail.com>
"A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders,
give orders, cooperate, act alone, solve equations, analyze a new
problem, pitch manure, program a computer, cook a tasty meal, fight
efficiently, die gallantly. Specialization is for insects."
-Robert Heinlein
next prev parent reply other threads:[~2007-08-22 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 15:33 git-svnimport: what to do after -i? Jing Xue
2007-08-22 16:58 ` Steven Walter [this message]
2007-08-22 17:04 ` Jing Xue
2007-08-23 1:28 ` Jing Xue
2007-08-23 7:29 ` Julian Phillips
2007-08-23 13:00 ` Jing Xue
2007-08-24 0:18 ` Julian Phillips
2007-08-24 1:06 ` Jing Xue
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=20070822165846.GA17815@dervierte \
--to=stevenrwalter@gmail.com \
--cc=git@vger.kernel.org \
--cc=jingxue@digizenstudio.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 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.