From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: git@vger.kernel.org
Subject: Problems getting rid of large files using git-filter-branch
Date: Tue, 6 Jan 2009 22:59:44 +0100 [thread overview]
Message-ID: <c09652430901061359q7a02291fk656ab23e54b19f5e@mail.gmail.com> (raw)
I'm trying to get rid of some large objects in my .git repository
using git-filter-branch. These are remnants from conversion from
CVS.
Q1: How can I figure out what it is in .git that takes so much space?
Q2: Where can I read more about what to do after running git-filter-branch to
removing the offending objects?
1. I ran this command to get rid of the offending files and that appears to
have worked. I can't find any traces of them anymore...
git filter-branch --tree-filter 'find . -regex ".*toolchain\..*" -exec
rm -f {} \;' HEAD
2. Running "git gc" takes a few seconds. The repository is still
huge(it should be
perhaps 10-20mByte).
du -skh .git/
187M .git/
3. I tried "git reflog expire --all" + lots of other tricks in the
link below, but no luck.
I tried the tricks I could find in this thread, but no luck:
http://article.gmane.org/gmane.comp.version-control.git/60219/match=trying+use+git+filter+branch+compress
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
next reply other threads:[~2009-01-06 22:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 21:59 Øyvind Harboe [this message]
2009-01-06 22:20 ` Problems getting rid of large files using git-filter-branch Johannes Schindelin
2009-01-06 22:36 ` Øyvind Harboe
2009-01-07 10:07 ` Johannes Schindelin
2009-01-07 10:15 ` Øyvind Harboe
2009-01-07 12:45 ` Johannes Schindelin
2009-01-07 18:18 ` Sitaram Chamarty
2009-01-06 22:31 ` Nicolas Pitre
2009-01-06 22:41 ` Øyvind Harboe
2009-01-06 23:17 ` Stephen R. van den Berg
2009-01-07 0:56 ` Nicolas Pitre
2009-01-07 8:26 ` Øyvind Harboe
2009-01-07 15:02 ` Nicolas Pitre
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=c09652430901061359q7a02291fk656ab23e54b19f5e@mail.gmail.com \
--to=oyvind.harboe@zylin.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).