Re: Truncating and cleaning a imported git repositary to make it more usable

From: Jakub Narebski <jnareb@gmail.com>
Date: Mar 29, 2008, 14:30 UTC
Message-ID: <fsljpe$i9o$1@ger.gmane.org>
In-Reply-To: <b2cdc9f30803290647n31bd6db5r4f346360989c2dcd@mail.gmail.com>

Alex Bennee wrote:

Show 22 quoted lines

> 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?

Did you pruned the repo ("git gc --prune" or "git prune")?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git