From: Jeff King <peff@peff.net>
To: Abscissa <bus_nabble_git@semitwist.com>
Cc: git@vger.kernel.org
Subject: Re: SVN -> Git *but* with special changes
Date: Wed, 28 Sep 2011 15:04:45 -0400 [thread overview]
Message-ID: <20110928190445.GC1482@sigill.intra.peff.net> (raw)
In-Reply-To: <1317227849979-6840904.post@n2.nabble.com>
On Wed, Sep 28, 2011 at 09:37:29AM -0700, Abscissa wrote:
> 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).
The usual technique is to put an empty .gitignore file into the empty
directory, which will make sure it always exists. If you import with
git-svn, it supports "--preserve-empty-dirs", which will do this for you
automatically.
> 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.
git-svn --ignore-paths will handle this for you.
Side note on the GitHub thing: all of the forks will share objects, so
it's not much as space as you might think. And all of the paid plans
count repos, not bytes. Of course, the painful part is probably cloning
the big objects to everybody's workstation. :)
> (Also, there are tags and branches to be converted too, in the
> SVN-standard "tags" and "branches" directories.)
git svn --stdlayout ?
-Peff
next prev parent reply other threads:[~2011-09-28 19: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 [this message]
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=20110928190445.GC1482@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=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).