From: Andreas Ericsson <ae@op5.se>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Elijah Newren <newren@gmail.com>,
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, 08 Oct 2007 11:23:27 +0200 [thread overview]
Message-ID: <4709F70F.4040700@op5.se> (raw)
In-Reply-To: <20071008061511.GA2859@steel.home>
Alex Riesen wrote:
> Elijah Newren, Mon, Oct 08, 2007 02:09:50 +0200:
>> On 10/7/07, Alex Riesen <raa.lkml@gmail.com> wrote:
>>> you missed something. Your example compresses to about 124k.
>> What version of git are you running? I reran all the steps to which
>
> git version 1.5.3.4.225.g31b973 (irrelevant custom modifications)
>
>> you responded (repeated below for clarity) with git-1.5.3.3 and still
>> get 11MB. Also, you must have different filesystem extents than me
>> since an empty git repo takes 196k here[1], so I don't think any repo
>> is going to get down to 124k.
>
> it is ext3. I do not install the hooks (~8k apparent, ~32k fs blocks)
> and never activate logs by default.
>
>> # Use vi to remove the line referring to refs/original...
>> git reflog expire --all
>
> another part of the suggestion re reflogs was to look into the logs,
> to check if expire actually removed anything. It seems to have been
> the culprit.
>
On my system, running git version 1.5.3.3.131.g34c6d,
git reflog expire --all
does absolutely nothing.
git reflog expire --expire=0 --all
truncates all the reflogs. I'm not sure if this is intended or not.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-10-08 9:23 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
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 [this message]
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=4709F70F.4040700@op5.se \
--to=ae@op5.se \
--cc=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=raa.lkml@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 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).