From: Enrico Weigelt <enrico.weigelt@vnc.biz>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git list <git@vger.kernel.org>
Subject: Re: filter-branch IO optimization
Date: Fri, 12 Oct 2012 16:49:54 +0200 (CEST) [thread overview]
Message-ID: <9de87aac-7e15-48d9-832a-e9a030c5ed43@zcs> (raw)
In-Reply-To: <878vbc21f3.fsf@pctrast.inf.ethz.ch>
Hi,
> The usual advice is "use an index-filter instead". It's *much*
> faster
> than a tree filter. However:
I've tried the last example from git-filter-branch manpage, but failed.
Seems like the GIT_INDEX_FILE env variable doesnt get honoured by
git-update-index, no index.new file created, and so mv call fails.
My second try (as index-filter command) was:
git ls-files -s > ../_INDEX_TMP
cat ../_INDEX_TMP |
sed "s-\t\"*-&addons/-" |
git update-index --index-info
rm -f ../_INDEX_TMP
It works fine in the worktree (i see files renamed in the index),
but no success when running it as --index-filter. Seems the index
file isn't used at all (or some completely different one).
By the way, inside the index filter, GIT_INDEX_FILTER here is
/home/devel/vnc/openerp/workspace/pkg/openerp-extra-bundle.git/.git-rewrite/t/../index
Obviously a different (temporary) index file, while many examples
on the web, suggesting to use commands like 'git add --cached' or
'git rm --cached' _without_ passing GIT_INDEX_FILTER variable.
Could there be some bug that this variable isn't honored properly
everywhere ?
--
Mit freundlichen Grüßen / Kind regards
Enrico Weigelt
VNC - Virtual Network Consult GmbH
Head Of Development
Pariser Platz 4a, D-10117 Berlin
Tel.: +49 (30) 3464615-20
Fax: +49 (30) 3464615-59
enrico.weigelt@vnc.biz; www.vnc.de
next prev parent reply other threads:[~2012-10-12 14:50 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
2012-10-12 14:49 ` Enrico Weigelt [this message]
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=9de87aac-7e15-48d9-832a-e9a030c5ed43@zcs \
--to=enrico.weigelt@vnc.biz \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.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