From: "James Sadler" <freshtonic@gmail.com>
To: git@vger.kernel.org
Subject: git filter-branch --subdirectory-filter
Date: Fri, 9 May 2008 11:01:47 +1000 [thread overview]
Message-ID: <e5e204700805081801x314b02bek5d53a086b02dac83@mail.gmail.com> (raw)
Hi All,
I have some issues with git filter-branch.
I have a git repository that I wish to split into multiple seperate
repositories for each logical
module that it contains. Each logical module is already in its own
directory at the root of the repo.
My experiments with 'git filter-branch' have been *partially* successful.
To extract a module into its own repo, I first copied the original
repo (this was a simple cp -r,
as it seemed to be the simplest way as git clone doesn't get all the branches)
and ran filter-branch with a --commit-filter to skip commits that were
irrelevant to th subdir.
That step worked just fine.
The next pass was to 'hoist' the contents of the subdir in the new
repo into the root dir.
I thought I could do this with a --subdirectory-filter argument to
filter-branch, except when I do
this, I loose tons of commits. (The working tree is correct, i.e. the
same as the original repo
working tree, but the history is screwed).
Anybody have any idea what I am doing wrong? If it can't be done with
--subdirectory-filter can
it be done with the 'subtree' merge strategy somehow?
Cheers,
--
James
next reply other threads:[~2008-05-09 1:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 1:01 James Sadler [this message]
2008-05-09 1:33 ` git filter-branch --subdirectory-filter Jeff King
2008-05-09 7:38 ` James Sadler
2008-05-09 7:57 ` Johannes Sixt
2008-05-09 8:00 ` Jeff King
2008-05-10 3:31 ` James Sadler
2008-05-10 5:53 ` Jeff King
2008-05-10 7:10 ` James Sadler
2008-05-10 11:38 ` James Sadler
2008-05-10 11:44 ` Jeff King
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=e5e204700805081801x314b02bek5d53a086b02dac83@mail.gmail.com \
--to=freshtonic@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 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).