public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Eric Niebler <eric@boostpro•com>
To: git@vger•kernel.org
Subject: help moving boost.org to git
Date: Mon, 05 Jul 2010 10:16:36 -0400	[thread overview]
Message-ID: <4C31E944.30801@boostpro.com> (raw)

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. Boost can then be a stitching-together of these, using
submodules or something (opinions welcome). It's an old project with
lots of history that we don't want to lose. The naive approach of simply
forking into N repositories for the N libraries and deleting the
unwanted files in each is unworkable because we'll end up with all the
history duplicated everywhere ... >100 repositories, each larger than 100Mb.

So, what are the options? Can I somehow delete from each repository the
history that is irrelevant? Is these some feature of git I don't know
about that can solve this problem for us?

(Caveat: I'm new to git and still getting up to speed. An acceptable
answer is: go off an learn about feature X and come back to us.)

At boost, We've already discussed a few possible approaches. Feel free
to comment and/or criticize any of the solutions suggested here:

  http://github.com/ryppl/ryppl/issues#issue/4

-- 
Eric Niebler
BoostPro Computing
http://www.boostpro.com

next             reply	other threads:[~2010-07-05 14:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 14:16 Eric Niebler [this message]
2010-07-05 14:48 ` help moving boost.org to git Erik Faye-Lund
2010-07-05 14:48 ` Johannes Sixt
2010-07-05 17:51   ` Eric Niebler
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=4C31E944.30801@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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox