Re: speed of git reset -- file

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: May 31, 2011, 22:13 UTC
Message-ID: <vpqr57e1pt8.fsf@bauges.imag.fr>
In-Reply-To: <7vpqmyilj6.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 13 quoted lines

> Jeff King <peff@peff.net> writes:
>
>> Conceptually, no, I don't think so.
>
> Hmm, don't we have to say like all other reset types which paths are
> dirty, i.e.
>
>   $ git reset HEAD -- diff.c
>   Unstaged changes after reset:
>   M       diff.c
>   M       diff.h
>
> which would mean we would need to refresh the index anyway?

This reminder is handy, but I can understand that people with really big trees whish to stat all the files only as needed (and would need to run "git status" by hand when needed). We can imagine a config variable like core.IHaveAReallyBigTree or so disabled by default for such cases.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/