Re: inotify to minimize stat() calls

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 14, 2013, 16:31 UTC
Message-ID: <7vpq023lhd.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CACBZZX6BVuQWtrLuTVXZo+77sT4yZQ3pvN=_fMma24-zd0NNqA@mail.gmail.com>

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

Show 8 quoted lines

> I looked into this a long while ago and remembered that rebase was
> doing something like a git status for every commit that it made to
> check the dirtyness.
>
> This could be vastly improved by having an unsafe option to git-rebase
> where it just assumes that the starting state + whatever it wrote out
> is the current state, i.e. it would break if someone stuck up on your
> checkout during an interactive rebase and changed a file,...

You could make it a lot safer than "just assumes", and the result may become generally usable, I think. For example, you can set a "magic" bit somewhere in $GIT_DIR/rebase-i while you are in "I am doing pick/pick/pick and the user will not interfere me" mode, and clear that bit upon "rebase --continue". And you cheat only while that "magic" bit is set.