From: Thomas Rast <trast@student.ethz.ch>
To: Enrico Weigelt <enrico.weigelt@vnc.biz>
Cc: git list <git@vger.kernel.org>
Subject: Re: filter-branch IO optimization
Date: Thu, 11 Oct 2012 22:34:24 +0200 [thread overview]
Message-ID: <878vbc21f3.fsf@pctrast.inf.ethz.ch> (raw)
In-Reply-To: <fa1e05a5-54b3-47ff-bd28-dc463ebbc4bd@zcs> (Enrico Weigelt's message of "Thu, 11 Oct 2012 17:39:47 +0200 (CEST)")
Enrico Weigelt <enrico.weigelt@vnc.biz> writes:
> for certain projects, I need to regularily run filter-branch on quite
> large repos (>10k commits), and that needs to be run multiple times,
> which takes several hours, so I'm looking for optimizations.
[...]
> #2: run a tree-filter which:
> * removes all files not belonging to the wanted module
> * move the module directory under another subdir (./addons/)
> * fix author/comitter name/email if empty (because otherwise fails)
The usual advice is "use an index-filter instead". It's *much* faster
than a tree filter. However:
> * fix charater sets and indentions of source files
That last step is rather crazy. At the very least you will want to only
operate on files that were changed since the parent commit, so as to
avoid scanning the whole tree. If you do this right, it should also fit
into an index-filter.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-10-11 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7e000a0f-9e4e-4a4d-a8ce-5d017e17939c@zcs>
2012-10-11 15:39 ` filter-branch IO optimization Enrico Weigelt
2012-10-11 18:36 ` Johannes Sixt
2012-10-11 20:34 ` Thomas Rast [this message]
2012-10-12 14:49 ` Enrico Weigelt
2012-10-12 15:59 ` Enrico Weigelt
2012-10-12 17:20 ` Enrico Weigelt
2012-10-12 17:20 ` 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=878vbc21f3.fsf@pctrast.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=enrico.weigelt@vnc.biz \
--cc=git@vger.kernel.org \
/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).