From: "Alex Bennee" <kernel-hacker@bennee.com>
To: "Johannes Sixt" <j.sixt@viscovery.net>
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: Sat, 29 Mar 2008 13:47:01 +0000 [thread overview]
Message-ID: <b2cdc9f30803290647n31bd6db5r4f346360989c2dcd@mail.gmail.com> (raw)
In-Reply-To: <47ED204E.3020602@viscovery.net>
On Fri, Mar 28, 2008 at 4:43 PM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> Alex Bennee schrieb:
> You really shouldn't do it this way, unless you do it on a ramdisk. Better
> use an --index-filter. This is modeled after the last example in the man
> page (and, of course, untested):
>
> git filter-branch --index-filter \
> 'git ls-files -s |
> grep -v " big_dira" |
> grep -v " big_dirb" |
> GIT_INDEX_FILE=$GIT_INDEX_FILE.new \
> git update-index --index-info &&
> mv $GIT_INDEX_FILE.new $GIT_INDEX_FILE' HEAD
>
> where the space before big_dir is actually a literal TAB!
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?
--
Alex, homepage: http://www.bennee.com/~alex/
next prev parent reply other threads:[~2008-03-29 13:47 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 [this message]
2008-03-29 14:30 ` Jakub Narebski
2008-03-31 6:17 ` Johannes Sixt
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=b2cdc9f30803290647n31bd6db5r4f346360989c2dcd@mail.gmail.com \
--to=kernel-hacker@bennee.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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).