From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH 1/3] Add --blob-filter option to filter-branch.
Date: Wed, 23 Apr 2008 21:05:19 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0804232104160.20267@eeepc-johanness> (raw)
In-Reply-To: <1208979757-30860-1-git-send-email-apenwarr@gmail.com>
Hi,
On Wed, 23 Apr 2008, Avery Pennarun wrote:
> From: Jeff King <peff@peff.net>
>
> On Tue, Apr 22, 2008 at 12:51:14PM -0400, Avery Pennarun wrote:
>
> > Do you think git would benefit from having a generalized version of
> > this script? Basically, the user provides a "munge" script on the
> > command line, and there's a git-filter-branch mode for auto-munging
> > (with a cache) every file in every checkin. Even if it's *only* ever
> > used for CRLF, I can imagine this being useful to a lot of people.
>
> It was easy enough to work up the patch below, which allows
>
> git filter-branch --blob-filter 'tr a-z A-Z'
>
> However, it's _still_ horribly slow. Shell script is nice and flexible,
> but running a tight loop like this is just painful. I suspect
> filter-branch in something like perl would be a lot faster and just as
> flexible (you could even do it in C, but you'd probably have to invent a
> little domain-specific scripting language).
>
> It is still much better performance than a tree filter, though:
>
> $ cd git && time git filter-branch --tree-filter '
> find . -type f | while read f; do
> tr a-z A-Z <"$f" >tmp
> mv tmp "$f"
> done
> ' HEAD~10..HEAD
>
> real 4m38.626s
> user 1m32.726s
> sys 2m51.163s
>
> $ cd git && git filter-branch --blob-filter 'tr a-z A-Z' HEAD~10..HEAD
> real 1m40.809s
> user 0m36.822s
> sys 1m14.273s
>
> Lots of system time in both. I'm sure we spend a fair bit of time
> hitting our very large map and blob-cache directories, which would be
> much more nicely implemented as associative arrays in memory (if we were
> using a more featureful language).
>
> Anyway, here is the patch. I don't know if it is even worth applying,
> since it is still painfully slow.
Not all of this belongs in the commit messaage.
> Acked-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This does.
A good general rule is: if you think it would be funny/strange to read
this message in the output of "git log", it should be changed.
Ciao,
Dscho
next prev parent reply other threads:[~2008-04-23 20:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 19:42 [PATCH 1/3] Add --blob-filter option to filter-branch Avery Pennarun
2008-04-23 19:42 ` [PATCH 2/3] Make filter-branch --glob-filter much faster by not calling 'cat' Avery Pennarun
2008-04-23 19:42 ` [PATCH 3/3] Update documentation to describe git filter-branch --blob-filter Avery Pennarun
2008-04-23 20:05 ` Johannes Schindelin [this message]
2008-04-23 20:12 ` [PATCH 1/3] Add --blob-filter option to filter-branch Avery Pennarun
2008-04-23 20:14 ` Johannes Schindelin
2008-04-23 20:18 ` [PATCH 1/3 v2] " Avery Pennarun
2008-04-23 20:22 ` Johannes Schindelin
2008-04-23 21:55 ` Jeff King
2008-04-23 22:07 ` Avery Pennarun
2008-04-24 1:33 ` Jeff King
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=alpine.DEB.1.00.0804232104160.20267@eeepc-johanness \
--to=johannes.schindelin@gmx.de \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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