From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
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, 8 Oct 2007 02:06:21 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710080204140.4174@racer.site> (raw)
In-Reply-To: <20071008010033.GA25654@fieldses.org>
Hi,
On Sun, 7 Oct 2007, J. Bruce Fields wrote:
> On Mon, Oct 08, 2007 at 01:34:07AM +0100, Johannes Schindelin wrote:
> > It does what it should do. It is _your_ task to look at refs/original/*
> > if everything went alright. Then you just delete the checked refs.
>
> It seems odd to me, by the way, that filter-branch has its own
> home-grown backup mechanism. Lots of other commands can "lose" commits,
> but none of them keep an extra backup like this.
The rationale was this: filter-branch recently learnt how to rewrite many
branches, and it might be tedious to find out which ones. But then, there
is git log --no-walk --all, so maybe I really should get rid of
refs/original/*?
I'd like to have some comments from the heavier filter-branch users on
that...
Ciao,
Dscho
next prev parent reply other threads:[~2007-10-08 1:06 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
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 [this message]
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=Pine.LNX.4.64.0710080204140.4174@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=bfields@fieldses.org \
--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 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).