Re: Really remove a file ?
- From
- marcreddist@aim.com <marcreddist@aim.com>
- Date
- Oct 10, 2008, 09:38 UTC
- Message-ID
- <8CAF8D313562BEE-1588-259E@webmail-da15.sysops.aol.com>
- In-Reply-To
- <d4bc1a2a0810091643u3903a1f4h44d3579b98fe6922@mail.gmail.com>
Hi,
Thank you both, that's exactly what i needed.
In case someone finds this post in the future, this :
> $ git filter-branch --index-filter 'git update-index --remove
' --force -- --all
worked perfectly. Although, it told me that git can't work on a dirty directory so I did this :
$ git add .
$ git commit
And after the filter-branch
$ git reset --hard HEAD^
> You'll probably also want to run "git gc" on your repo to
> actually get rid of the huge object that was added (or does
> filter-branch do this automatically?).
I'm not sure it's required by git-filter-branch alone. In this case :
git-gc saves almost 5% after the file deletion
it saves 4.5% before the file deletion
If I run git gc before and after the git filter-branch, it saves 4.5% and then 0.2%.
But maybe my tests applies to my particular environment and cannot be generalized.
Thank you again for the help.
Take care,
Marc, happy git user.