From: Nils Homer <nilshomer@gmail.com>
To: <git@vger.kernel.org>
Subject: Re: How to delete large files
Date: Fri, 02 Oct 2009 12:20:58 -0700 [thread overview]
Message-ID: <C6EBA0AA.D7D3%nilshomer@gmail.com> (raw)
In-Reply-To: <4AC6031A.2070409@viscovery.net>
Thank-you for all of your insightful help. Combining all the advice, the
commands that worked are:
git filter-branch --index-filter "git rm -rf --cached --ignore-unmatch
$files" --tag-name-filter cat -- --all
git -rf .git/refs/original
git reflog expire --expire=now
git gc --prune=now
I then cloned the repository to a different location and replaced my
centralized version with the cloned copy.
Thanks,
Nils
On 10/2/09 6:41 AM, "Johannes Sixt" <j.sixt@viscovery.net> wrote:
> Mikael Magnusson schrieb:
>> Well, you just gave "HEAD" to git filter-branch to rewrite, i think
>> you want --all to rewrite all refs you have.
>
> ... and '--tag-filter cat' to rewrite tags as well.
>
> -- Hannes
prev parent reply other threads:[~2009-10-02 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 10:03 How to delete large files Nils Homer
2009-10-02 11:41 ` Matthieu Moy
2009-10-02 12:26 ` Mikael Magnusson
2009-10-02 13:41 ` Johannes Sixt
2009-10-02 19:20 ` Nils Homer [this message]
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=C6EBA0AA.D7D3%nilshomer@gmail.com \
--to=nilshomer@gmail.com \
--cc=git@vger.kernel.org \
/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).