From: Jing Xue <jingxue@digizenstudio.com>
To: git@vger.kernel.org
Subject: Re: git-svnimport: what to do after -i?
Date: Wed, 22 Aug 2007 21:28:36 -0400 [thread overview]
Message-ID: <20070823012836.GA18796@falcon.digizenstudio.com> (raw)
In-Reply-To: <20070822113325.1bihryuk4gko8kgs@intranet.digizenstudio.com>
OK, got it working. It had more to do with the module/trunk path than
the -i.
My svn projects are organized like:
projectFoo
-trunk
-tags
-branches
So I initially used:
git svnimport -C projectFoo -r -A svn-authors -I .gitignore -T projectFoo svn://jabba trunk
which resulted in the empty working directory - with or without the -i.
What ended up working is this:
git svnimport -C projectFoo -r -A svn-authors -I .gitignore -T projectFoo -P trunk svn://jabba
Cheers.
--
Jing Xue
next prev parent reply other threads:[~2007-08-23 1:28 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
2007-08-22 17:04 ` Jing Xue
2007-08-23 1:28 ` Jing Xue [this message]
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=20070823012836.GA18796@falcon.digizenstudio.com \
--to=jingxue@digizenstudio.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).