From: "Elijah Newren" <newren@gmail.com>
To: "Dmitry Potapov" <dpotapov@gmail.com>
Cc: "Alex Riesen" <raa.lkml@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: Sun, 7 Oct 2007 18:22:28 -0600 [thread overview]
Message-ID: <51419b2c0710071722k576c06d9i2f4dce730eae2059@mail.gmail.com> (raw)
In-Reply-To: <20071007234346.GA29433@potapov>
On 10/7/07, Dmitry Potapov <dpotapov@gmail.com> wrote:
> On Sun, Oct 07, 2007 at 04:24:49PM -0600, Elijah Newren wrote:
> > $ git reflog expire --all
> > $ git gc --aggressive --prune
>
> I believe this should work:
>
> git reflog expire --all --expire-unreachable=0
> git gc --prune
Yes, this seems to work. So the history-rewriting steps are
git-filter-branch --tree-filter 'rm -f testme.txt' HEAD
git reset --hard
rm -rf .git/refs/original/
vi .git/packed-refs
# Use vi to remove the line referring to refs/original...
git reflog expire --all --expire-unreachable=0
git gc --prune
Seems like a wrapper is needed. :-)
> Warning: all unreachable references will be removed!
What other scenarios could lead to unreachable references? I don't
know how to determine whether this is safe or not (except that these
were test repositories anyway, so I don't care what happens to them).
Thanks!
Elijah
next prev parent reply other threads:[~2007-10-08 0:22 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
2007-10-07 23:43 ` Dmitry Potapov
2007-10-08 0:22 ` Elijah Newren [this message]
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=51419b2c0710071722k576c06d9i2f4dce730eae2059@mail.gmail.com \
--to=newren@gmail.com \
--cc=dpotapov@gmail.com \
--cc=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--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).