From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Re: Remove "historical" objects from repository to save place
Date: Sat, 21 Jan 2006 12:25:57 -0800 [thread overview]
Message-ID: <7virsdl44q.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060121200615.GM28365@pasky.or.cz> (Petr Baudis's message of "Sat, 21 Jan 2006 21:06:15 +0100")
Petr Baudis <pasky@suse.cz> writes:
>> You might be able to cauterize the history at a specific commit
>> and then re-clone. I've talked about how in "[QUESTION] about
>> .git/info/grafts file" thread yesterday, so I won't repeat that.
>
> Shouldn't the git-prune be sufficient after cauterizing the history?
Logically yes, but practically no.
Most likely what the original requestor cloned from Linus has
been already packed so git-prune would not do much.
next prev parent reply other threads:[~2006-01-21 20:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 19:18 Remove "historical" objects from repository to save place Andrey Borzenkov
2006-01-21 19:58 ` Junio C Hamano
2006-01-21 20:06 ` Petr Baudis
2006-01-21 20:25 ` Junio C Hamano [this message]
2006-01-21 20:49 ` Randal L. Schwartz
2006-01-21 21:46 ` Junio C Hamano
2006-01-21 23:27 ` Andrey Borzenkov
2006-01-21 21:46 ` Andrey Borzenkov
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=7virsdl44q.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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).