From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: New command/tool: git filter-repo
Date: Thu, 31 Jan 2019 11:09:39 -0800 [thread overview]
Message-ID: <xmqq36p83aq4.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CABPp-BFC--s+D0ijRkFCRxP5Lxfi+__YF4EdxkpO5z+GoNW7Gg@mail.gmail.com> (Elijah Newren's message of "Thu, 31 Jan 2019 00:57:36 -0800")
Elijah Newren <newren@gmail.com> writes:
> git-filter-repo[1], a filter-branch-like tool for rewriting repository
> history, is ready for more widespread testing and feedback. The rough
> edges I previously mentioned have been fixed, and it has several useful
> features already, though more development work is ongoing (docs are a
> bit sparse right now, though -h provides some help).
>
> Why filter-repo vs. filter-branch?
How does it compare with bfg-repo-cleaner? Somehow I was led to
believe that all serious users of filter-branch like functionality
are using bfg-repo-cleaner instead.
next prev parent reply other threads:[~2019-01-31 19:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 8:57 New command/tool: git filter-repo Elijah Newren
2019-01-31 19:09 ` Junio C Hamano [this message]
2019-01-31 20:43 ` Elijah Newren
2019-01-31 23:36 ` Roberto Tyley
2019-02-01 7:38 ` Elijah Newren
2019-01-31 20:47 ` Elijah Newren
2019-02-08 1:25 ` Elijah Newren
2019-02-08 10:22 ` Johannes Schindelin
2019-02-08 18:53 ` Ævar Arnfjörð Bjarmason
2019-02-08 20:13 ` Johannes Schindelin
2019-02-11 16:00 ` Elijah Newren
2019-02-11 15:47 ` Elijah Newren
2019-06-08 16:20 ` Elijah Newren
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq36p83aq4.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).