From: Jonathan Nieder <jrnieder@gmail.com>
To: Roberto Tyley <roberto.tyley@gmail.com>
Cc: git@vger.kernel.org, peff@peff.net, tr@thomasrast.ch
Subject: Re: [PATCH] docs: add filter-branch note about The BFG
Date: Tue, 17 Dec 2013 10:40:03 -0800 [thread overview]
Message-ID: <20131217184003.GJ2311@google.com> (raw)
In-Reply-To: <1387277599-69719-1-git-send-email-roberto.tyley@gmail.com>
Hi,
Roberto Tyley wrote:
> The BFG is a tool specifically designed for the task of removing
> unwanted data from Git repository history - a common use-case for which
> git-filter-branch has been the traditional workhorse.
>
> It's beneficial to let users know that filter-branch has an alternative
> here:
That sounds like a good suggestion for the SEE ALSO section, or an
explanation of when each tool should be used would be a good thing to
put in NOTES, but...
[...]
> --- a/Documentation/git-filter-branch.txt
> +++ b/Documentation/git-filter-branch.txt
> @@ -18,6 +18,12 @@ SYNOPSIS
>
> DESCRIPTION
> -----------
> +
> +NOTE: For simply removing unwanted data from repository history, you may
> +want to use link:http://rtyley.github.io/bfg-repo-cleaner/[The BFG Repo-Cleaner]
> +instead - it's generally faster and simpler for eliminating large files
> +or private data.
... this shouting NOTE at the top of the description is way over the
top.
So as is, this patch looks like a net negative.
Thanks and hope that helps,
Jonathan
prev parent reply other threads:[~2013-12-17 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 10:53 [PATCH] docs: add filter-branch note about The BFG Roberto Tyley
2013-12-17 18:13 ` Junio C Hamano
2013-12-18 1:04 ` Roberto Tyley
2013-12-18 5:57 ` Junio C Hamano
2013-12-18 14:25 ` [PATCH v2] Tweaked notes on gfb<->bfg differences Roberto Tyley
2013-12-18 14:25 ` [PATCH v2] docs: add filter-branch notes on The BFG Roberto Tyley
2013-12-17 18:40 ` Jonathan Nieder [this message]
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=20131217184003.GJ2311@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=roberto.tyley@gmail.com \
--cc=tr@thomasrast.ch \
/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).