From: Josef Wolf <jw@raven.inka.de>
To: git@vger.kernel.org
Subject: Trying to split repository
Date: Thu, 1 Oct 2009 18:03:35 +0200 [thread overview]
Message-ID: <20091001160335.GA26068@raven.wolf.lan> (raw)
Hello,
One of my repositories has grown a subdirectory that I'd like to split off,
so other can use it as a subproject. With the help of google, I found this
solution:
# first extract the library from the original repository
#
git clone --no-hardlinks repository library.tmp
(
cd library.tmp
git filter-branch --subdirectory-filter CF -- --all
git reset --hard
git gc --aggressive
git prune
git gc
git clone --bare . ../library
)
rm -rf library.tmp
# Now remove the library from the original repository, so it can be
# included as a subproject
#
git clone --no-hardlinks repository repository.new.tmp
(
cd repository.new.tmp
git filter-branch \
--index-filter "git rm -r -f --cached --ignore-unmatch CF" \
-- --all
git reset --hard
git gc --aggressive
git prune
git gc
git clone --bare . ../repository.new
)
rm -rf repository.new.tmp
This works fine. But there's one problem, though. "gitk --all" in the new
repository still shows all the history of the removed library. The patch
show no modifications, but the log entry is still there.
Any hints how to get rid of those log entries?
next reply other threads:[~2009-10-01 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 16:03 Josef Wolf [this message]
2009-10-01 16:49 ` Trying to split repository Adam Brewster
2009-10-01 21:13 ` Josef Wolf
2009-10-02 0:47 ` Adam Brewster
2009-10-02 0:52 ` [PATCH] filter-branch: add --prune-empty to option summary Adam Brewster
2009-10-02 7:45 ` Jeff King
2009-10-02 14:18 ` Adam Brewster
2009-10-02 15:42 ` Trying to split repository Josef Wolf
2009-10-01 16:49 ` Tomas Carnecky
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=20091001160335.GA26068@raven.wolf.lan \
--to=jw@raven.inka.de \
--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).