From: Abscissa <bus_nabble_git@semitwist.com>
To: git@vger.kernel.org
Subject: Re: SVN -> Git *but* with special changes
Date: Sat, 7 Jan 2012 21:03:51 -0800 (PST) [thread overview]
Message-ID: <1325999031923-7163706.post@n2.nabble.com> (raw)
In-Reply-To: <20110928190445.GC1482@sigill.intra.peff.net>
>If you import with
>git-svn, it supports "--preserve-empty-dirs", which will do this for you
>automatically.
I came across this, and it seems to mostly work:
http://john.albin.net/git/git-svn-migrate
Except it fails to do the "--preserve-empty-dirs". It does say that it
passes any options it doesn't recognize directly to git-svn, so I gave it
that, but just got:
- Cloning repository...
Unknown option: preserve-empty-dirs
Now, I realize this isn't a forum for that particular "git-svn-migrate"
tool, and I don't expect anyone to go digging though it on my account, so
I'm willing to try to add it into the script if I can just find out the
proper way to use "--preserve-empty-dirs".
However, I suspect that script may not be my problem at all: If I do this:
git svn help | grep preserve
I get absolutely nothing. There doesn't seem to be a
"--preserve-empty-dirs".
--
View this message in context: http://git.661346.n2.nabble.com/SVN-Git-but-with-special-changes-tp6840904p7163706.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2012-01-08 5:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 16:37 SVN -> Git *but* with special changes Abscissa
2011-09-28 17:10 ` Stephen Bash
2011-09-28 17:44 ` Matthieu Moy
2011-09-28 19:07 ` Jeff King
2011-09-28 18:03 ` Abscissa
2012-01-07 22:30 ` Abscissa
2011-09-28 19:04 ` Jeff King
2012-01-08 5:03 ` Abscissa [this message]
2012-01-08 5:10 ` Jeff King
2012-01-08 5:17 ` Abscissa
2012-01-08 5:25 ` Abscissa
2012-01-08 10:33 ` Carlos Martín Nieto
2012-01-08 10:47 ` Andreas Schwab
2012-01-08 12:08 ` Adam Borowski
2012-01-08 22:28 ` Abscissa
2012-01-08 23:38 ` Abscissa
2012-01-12 21:52 ` Abscissa
2012-01-14 3:43 ` Abscissa
2012-01-09 8:26 ` Michael Haggerty
2012-01-08 11:24 ` Thomas Hochstein
2012-01-08 11:20 ` Thomas Hochstein
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=1325999031923-7163706.post@n2.nabble.com \
--to=bus_nabble_git@semitwist.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).