From: Alex Riesen <raa.lkml@gmail.com>
To: Elijah Newren <newren@gmail.com>
Cc: Frank Lichtenheld <frank@lichtenheld.de>, git@vger.kernel.org
Subject: Re: Trying to use git-filter-branch to compress history by removing large, obsolete binary files
Date: Mon, 8 Oct 2007 00:19:20 +0200 [thread overview]
Message-ID: <20071007221920.GF2765@steel.home> (raw)
In-Reply-To: <51419b2c0710071500x318ee734n9db6ca9e6daa3196@mail.gmail.com>
Elijah Newren, Mon, Oct 08, 2007 00:00:51 +0200:
> On 10/7/07, Frank Lichtenheld <frank@lichtenheld.de> wrote:
> > On Sun, Oct 07, 2007 at 03:23:59PM -0600, Elijah Newren wrote:
> > > The following set of instructions will duplicate my problem with a
> > > smaller repo; why is the local git repository bigger after running
> > > git-filter-branch rather than smaller as I'd expect? I'm probably
> > > missing something obvious, but I have no idea what it is.
> >
> > The usual suspect would be the reflog.
>
> The git-filter-branch documentation mentions creating refs/original
> under .git. Unfortunately, it doesn't contain any links or
> documentation on how I'd clean those out and I haven't been able to
> figure it out. I asked on #git how to clean these out and got some
> answers that didn't work (git branch -d and something else I don't
> remember).
rm -rf .git/refs/original/refs/heads/<the branch where HEAD pointed to>
(assuming you haven't repacked yet)
or just edit .git/packed-refs and remove everything "refs/original"
which fits the criteria
> So...how do I fix the reflog, and then repack to have a
> pack under 11MB in size?
git reflog expire --all (it is a bit to much. You can just edit
.git/logs/* in any text editor)
next prev parent reply other threads:[~2007-10-07 22:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 21:23 Trying to use git-filter-branch to compress history by removing large, obsolete binary files Elijah Newren
2007-10-07 21:38 ` Frank Lichtenheld
2007-10-07 22:00 ` Elijah Newren
2007-10-07 22:19 ` Alex Riesen [this message]
2007-10-07 22:24 ` Elijah Newren
2007-10-07 23:40 ` Alex Riesen
2007-10-08 0:09 ` Elijah Newren
2007-10-08 6:15 ` Alex Riesen
2007-10-08 9:23 ` Andreas Ericsson
2007-10-07 23:43 ` Dmitry Potapov
2007-10-08 0:22 ` Elijah Newren
2007-10-08 1:06 ` Dmitry Potapov
2007-10-08 9:27 ` Andreas Ericsson
2007-10-08 10:05 ` Karl Hasselström
2007-10-08 12:40 ` Dmitry Potapov
2007-10-08 13:01 ` Karl Hasselström
2007-10-07 23:19 ` Johannes Schindelin
2007-10-07 23:24 ` Elijah Newren
2007-10-07 23:28 ` Johannes Schindelin
2007-10-07 23:38 ` Elijah Newren
2007-10-08 0:34 ` Johannes Schindelin
2007-10-08 0:47 ` Elijah Newren
2007-10-08 2:28 ` Sam Vilain
2007-10-08 1:00 ` J. Bruce Fields
2007-10-08 1:06 ` Johannes Schindelin
2007-10-08 6:22 ` Johannes Sixt
2007-10-08 14:36 ` J. Bruce Fields
2007-10-08 16:37 ` Theodore Tso
2007-10-08 19:05 ` J. Bruce Fields
2007-10-09 10:37 ` Johannes Schindelin
2007-10-07 22:08 ` Alex Riesen
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=20071007221920.GF2765@steel.home \
--to=raa.lkml@gmail.com \
--cc=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.