git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evan Driscoll <driscoll@cs.wisc.edu>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Splitting up a repository
Date: Sat, 04 Dec 2010 00:19:10 -0600	[thread overview]
Message-ID: <4CF9DD5E.7020400@cs.wisc.edu> (raw)
In-Reply-To: <20101204053304.GA7311@sigill.intra.peff.net>

[-- Attachment #1: Type: text/plain, Size: 773 bytes --]

On 12/3/2010 23:33, Jeff King wrote:
>> Is there a better way than making several (recursive) copies of the
>> repository, deleting all but one directory in each copy, then moving the
>> contents of that directory up a level? (And perhaps setting up a Git
>> superproject at the original location. I do know about that.)
> 
> Rewrite the history of each directory with git-filter-branch. It even
> has a "--subdirectory-filter" option that will do exactly what you want.

Great, thanks. I had to mess around with a submodule that was inside one
of the subdirectories that didn't make it through the history rewrite,
and I could see that have getting slightly hairy, but at least in my
case it was pretty simple. Other than that, worked like a charm.

Evan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 543 bytes --]

  reply	other threads:[~2010-12-04  6:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-04  5:27 Splitting up a repository Evan Driscoll
2010-12-04  5:33 ` Jeff King
2010-12-04  6:19   ` Evan Driscoll [this message]
2010-12-04  7:09 ` Nguyen Thai Ngoc Duy
2010-12-04  7:14   ` Evan Driscoll
2010-12-04  7:41     ` Nguyen Thai Ngoc Duy

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=4CF9DD5E.7020400@cs.wisc.edu \
    --to=driscoll@cs.wisc.edu \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).