From: Johannes Sixt <j.sixt@viscovery.net>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: Avery Pennarun <apenwarr@gmail.com>, git@vger.kernel.org
Subject: Re: Truncating and cleaning a imported git repositary to make it more usable
Date: Mon, 31 Mar 2008 08:17:38 +0200 [thread overview]
Message-ID: <47F08202.9030206@viscovery.net> (raw)
In-Reply-To: <b2cdc9f30803290647n31bd6db5r4f346360989c2dcd@mail.gmail.com>
Alex Bennee schrieb:
> Hmm thats odd. Despite having successfully run the filter my repo is
> still the same size. git-fsck --full shows loads of dangling commits
> but I'm guessing because the repo is packed they don't get dropped. Is
> it possible to repack the whole repo or do you have to manually unpack
> the packs and re-pack?
Yes. Run git repack -a -d -f or create a local clone using the file protocol:
git clone file://$(pwd)/this that
(If you don't use the file protocol, git clone just hard-links the
repository, and you again don't get the reduced size.)
-- Hannes
next prev parent reply other threads:[~2008-03-31 6:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 12:35 Truncating and cleaning a imported git repositary to make it more usable Alex Bennee
2008-03-28 12:50 ` Avery Pennarun
2008-03-28 13:08 ` Alex Bennee
2008-03-28 15:52 ` Alex Bennee
2008-03-28 16:03 ` Alex Bennee
2008-03-28 16:43 ` Johannes Sixt
2008-03-28 18:07 ` [PATCH] Documentation: Another example for git-filter-branch Alex Bennee
2008-03-28 20:44 ` Truncating and cleaning a imported git repositary to make it more usable Mike Hommey
2008-03-29 13:47 ` Alex Bennee
2008-03-29 14:30 ` Jakub Narebski
2008-03-31 6:17 ` Johannes Sixt [this message]
2008-03-28 18:08 ` Jeff King
2008-03-28 18:19 ` Jeff King
2008-03-29 17:51 ` Michael Haggerty
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=47F08202.9030206@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=kernel-hacker@bennee.com \
/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).