From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Breaking up repositories
Date: Fri, 01 Jun 2007 12:25:29 +0200 [thread overview]
Message-ID: <f3orsv$97l$1@sea.gmane.org> (raw)
In-Reply-To: 465EEF96.6050307@freedesktop.org
Josh Triplett wrote:
> Jason Sewall wrote:
>> I recently imported my subversion repo with git-svn and I'm curious
>> what the best way to break up the monolithic repo (my many disparate
>> projects from my single svn repo) into individual git repos of their
>> own.
>
> In the specific case of git-svn, you can probably give git-svn the
> appropriate paths to import each project separately; that may do what you
> want, depending on your repository layout.
>
> In the general case, if you want to split a subtree of a git repo into a git
> repo, you want git-split, by Jamey Sharp and I:
> <http://people.freedesktop.org/~jamey/git-split>
> From a copy of the git repo you want to split, just run "git-split subdir",
> optionally with a newest and oldest commit, and it will output the sha1 of
> the new top commit for use as the new branch ref. Remove all other
> branches, reflogs, and other references to the old commits, and use prune
> or gc to get rid of old objects. Repeat as desired for other subdirs.
I have added info about git-split to Git Wiki
http://git.or.cz/gitwiki/InterfacesFrontendsAndTools
Please improve this information, and correct if it is wrong.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-06-01 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 15:53 Breaking up repositories Josh Triplett
2007-06-01 7:45 ` Andy Parkins
2007-06-01 10:25 ` Jakub Narebski [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-31 6:50 Jason Sewall
2007-05-31 13:55 ` Dave Hanson
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='f3orsv$97l$1@sea.gmane.org' \
--to=jnareb@gmail.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 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.