Alex Bennee wrote:
> On Fri, Mar 28, 2008 at 4:43 PM, Johannes Sixt <j.sixt@xxxxxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
