Re: speed of git reset -- file

Junio C Hamano [off-list ref] writes:

Jeff King [off-list ref] writes:

quoted

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/

On Wed, Jun 1, 2011 at 5:13 AM, Matthieu Moy
[off-list ref] wrote:

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.

git update-index --assume-unchanged and core.ignorestat?
-- 
Duy