From: Junio C Hamano <gitster@pobox.com>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: Rewriting history with git-filter-branch and leaking objects (?)
Date: Fri, 17 Aug 2007 14:11:55 -0700 [thread overview]
Message-ID: <7vzm0pg92c.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <86k5ruxdxz.fsf@lola.quinscape.zz> (David Kastrup's message of "Fri, 17 Aug 2007 19:34:32 +0200")
David Kastrup <dak@gnu.org> writes:
> Mike Hommey <mh@glandium.org> writes:
>
>> I've been playing with git-filter-branch, and was wondering how objects
>> from the original branch are supposed to be removed.
>>
>> It looks like removing the refs/original/* refs is not enough.
>>
>> And it also looks like when all references seem to be removed, git-prune
>> doesn't fully do its job...
>
> It is quite quite hard to get rid of objects. You need to get the
> reflogs for the commits and the files expired.
An easier way is probably to make a new clone in the
neighbouring directory locally.
next prev parent reply other threads:[~2007-08-17 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 17:18 Rewriting history with git-filter-branch and leaking objects (?) Mike Hommey
2007-08-17 17:34 ` David Kastrup
2007-08-17 17:46 ` Mike Hommey
2007-08-19 2:34 ` Sam Vilain
2007-08-17 21:11 ` Junio C Hamano [this message]
2007-08-17 18:31 ` Mike Hommey
2007-08-19 19:59 ` Mike Hommey
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=7vzm0pg92c.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=dak@gnu.org \
--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).