From: "Wesley J. Landaker" <wjl@icecavern.net>
To: carbonated beverage <ramune@net-ronin.org>
Cc: git@vger.kernel.org
Subject: Re: git-svn question
Date: Thu, 15 Jul 2010 12:50:31 -0600 [thread overview]
Message-ID: <201007151250.32974.wjl@icecavern.net> (raw)
In-Reply-To: <20100715171849.GA31823@heretic.net-ronin.org>
On Thursday, July 15, 2010 11:18:49 carbonated beverage wrote:
> I'm trying to figure out how to import a rather large SVN tree that has
> been around for a while, initially converted from CVS.
[...]
> Given multiple projects that are nested as such, is there a way to get
> git-svn to import the tree and be able to derive the tags and branches?
> Also, this tree is a little over 1TiB in size, though a large chunk of
> that is due to the duplicates made by SVN's branches/tags.
That sounds pretty messed up. Someone may have better advice, but I'd
probably approach it by doing one or more of the following:
1) Fix it up with svndumpfilter first to get rid of useless or duplicated
parts, then import it.
2) Once imported into use git rebase and/or git filter-branch to clean
things up until it's how you like it.
3) If all else fails, archive the SVN repository (or the git imported
equivalent), call it "old history", and then start over and manually import
only the active and useful branches and tags into git.
next prev parent reply other threads:[~2010-07-15 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 17:18 git-svn question carbonated beverage
2010-07-15 18:50 ` Wesley J. Landaker [this message]
[not found] <f2e8061d0612210927p2d18adb4u995ce16702fc3b08@mail.gmail.com>
2006-12-21 17:34 ` Joseph Carrafa
2006-12-21 18:21 ` Seth Falcon
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=201007151250.32974.wjl@icecavern.net \
--to=wjl@icecavern.net \
--cc=git@vger.kernel.org \
--cc=ramune@net-ronin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.