From: Jeff King <peff@peff.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Stephen Bash <bash@genarts.com>,
Abscissa <bus_nabble_git@semitwist.com>,
git@vger.kernel.org
Subject: Re: SVN -> Git *but* with special changes
Date: Wed, 28 Sep 2011 15:07:16 -0400 [thread overview]
Message-ID: <20110928190716.GD1482@sigill.intra.peff.net> (raw)
In-Reply-To: <vpq62kc36kn.fsf@bauges.imag.fr>
On Wed, Sep 28, 2011 at 07:44:24PM +0200, Matthieu Moy wrote:
> > I'd eliminate these on the SVN side before converting to Git. If you
> > have svnadmin access to the SVN repo svnadmin dump, svndumpfilter,
> > svnadmin load is a pretty easy process.
>
> Otherwise, you can do it on the Git side with:
>
> git filter-branch --tree-filter 'rm -f some-large-blob'
It's much more efficient to do:
git filter-branch --index-filter \
'git rm --cached --ignore-unmatch some-large-blob'
which avoids checking out the large files over and over[1], just to
delete them. Of course, it's even more efficient not to import them from
svn in the first place. :)
-Peff
[1] This is straight from the filter-branch manpage, btw.
next prev parent reply other threads:[~2011-09-28 19:07 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 [this message]
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=20110928190716.GD1482@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=bash@genarts.com \
--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).