From: Abscissa <bus_nabble_git@semitwist.com>
To: git@vger.kernel.org
Subject: SVN -> Git *but* with special changes
Date: Wed, 28 Sep 2011 09:37:29 -0700 (PDT) [thread overview]
Message-ID: <1317227849979-6840904.post@n2.nabble.com> (raw)
I have a couple big projects in SVN that I'd like to convert to Git. Being in
SVN, they've operated under a couple assumptions that are not true under
Git. These assumptions are:
1. Directories can exist even if there's nothing in them (just like any
filesystem).
2. Keeping binary files in version control isn't a big deal because the
whole repo doesn't get copied to everyone's system or use up people's GitHub
storage space.
The SVN repos have been relying on those, but both are false under Git, so I
need to do a "modified" conversion, rather than just a straight one.
So, how can I convert an SVN repo to Git, and have the conversion add dummy
files to empty directories and exclude specific files? (Also, there are tags
and branches to be converted too, in the SVN-standard "tags" and "branches"
directories.)
--
View this message in context: http://git.661346.n2.nabble.com/SVN-Git-but-with-special-changes-tp6840904p6840904.html
Sent from the git mailing list archive at Nabble.com.
next reply other threads:[~2011-09-28 16:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 16:37 Abscissa [this message]
2011-09-28 17:10 ` SVN -> Git *but* with special changes 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
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=1317227849979-6840904.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).