From: Johannes Sixt <j.sixt@viscovery.net>
To: Cap Petschulat <cap@naviasystems.com>
Cc: git@vger.kernel.org
Subject: Re: filter-branch --subdirectory-filter prematurely truncating history?
Date: Tue, 10 Mar 2009 08:00:09 +0100 [thread overview]
Message-ID: <49B60FF9.9020805@viscovery.net> (raw)
In-Reply-To: <loom.20090309T230424-857@post.gmane.org>
Cap Petschulat schrieb:
> I'd like to spin a subdirectory of an existing git repo off in to its
> own repo while preserving history. From what I've read, I should be
> able to do this with a fresh clone followed by git filter-branch
> --subdirectory-filter MYSUBDIR, assuming I don't care about other
> branches or tags. This runs, and when it's done, I have a repo that
> contains the subdir's contents as its root. So far so good.
>
> I would expect to see the subdir's full history when I run git log,
> but instead it cuts off prematurely, showing the first commit to be
> some relatively recent minor change I'll call FOO. In gitk, I can see
> that history prior to FOO is still around, but FOO has no parents, and
> the commit before FOO has no children. In the original repo, FOO's
> parent was the merge of a branch which no longer exists, if this
> matters.
A bug in this area was fixed in git v1.6.0-rc3. Which version are you using?
-- Hannes
next prev parent reply other threads:[~2009-03-10 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 23:08 filter-branch --subdirectory-filter prematurely truncating history? Cap Petschulat
2009-03-10 7:00 ` Johannes Sixt [this message]
2009-03-11 0:37 ` Cap Petschulat
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=49B60FF9.9020805@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=cap@naviasystems.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).