From: Eric Niebler <eric@boostpro•com>
To: git@vger•kernel.org
Subject: Re: help moving boost.org to git
Date: Mon, 05 Jul 2010 13:51:43 -0400 [thread overview]
Message-ID: <4C321BAF.8020303@boostpro.com> (raw)
In-Reply-To: <4C31F0D4.1040207@viscovery.net>
On 7/5/2010 10:48 AM, Johannes Sixt wrote:
> Am 7/5/2010 16:16, schrieb Eric Niebler:
>> I have a question about the best approach to take for refactoring a
>> large svn project into git. The project, boost.org, is a collection of
>> C++ libraries (>100) that are mostly independent. (There may be
>> cross-library dependencies, but we plan to handle that at a higher
>> level.) After the move to git, we'd like each library to be in its own
>> git repository.
>
> You could use svn2git: http://gitorious.org/svn2git
> KDE uses it to split its SVN repository into pieces. The tool is driven by
> a "ruleset" that specifies SVN subdirectories and revision numbers that
> make up a module.
I'm off to learn about filter-branch, tree-filter and svn2git. Thanks
for the suggestions. More questions to come, I'm sure.
--
Eric Niebler
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2010-07-05 17:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 14:16 help moving boost.org to git Eric Niebler
2010-07-05 14:48 ` Erik Faye-Lund
2010-07-05 14:48 ` Johannes Sixt
2010-07-05 17:51 ` Eric Niebler [this message]
2010-07-05 18:43 ` Sverre Rabbelier
2010-07-06 15:06 ` Raja R Harinath
2010-07-05 22:04 ` Finn Arne Gangstad
2010-07-05 23:11 ` Eric Niebler
2010-07-05 23:32 ` Avery Pennarun
2010-07-06 0:16 ` Eric Niebler
2010-07-06 17:27 ` Avery Pennarun
2010-07-06 18:00 ` Eric Niebler
2010-07-06 18:13 ` Avery Pennarun
2010-07-06 18:29 ` Eric Niebler
2010-07-06 1:46 ` Dave Abrahams
2010-07-06 8:51 ` Jakub Narebski
2010-07-06 10:34 ` David Abrahams
2010-07-06 0:16 ` Greg Troxel
2010-07-06 0:25 ` Eric Niebler
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=4C321BAF.8020303@boostpro.com \
--to=eric@boostpro$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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