From: Junio C Hamano <junkio@cox.net>
Date: Fri, 09 Feb 2007 20:22:48 GMT
Subject: Re: 'git status' is not read-only fs friendly
Message-ID: <7vr6szt71j.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.64.0702091148060.8424@woody.linux-foundation.org>

Linus Torvalds <torvalds@linux-foundation.org> writes:

> "git status" doesn't "pretend" to write stuff. It really does. 
>
> You *can* just use "git-runstatus" instead. That's the command that 
> actually does all the heavy lifting. But you can see the difference by 
> doing this:
>
> 	touch Makefile
> 	git runstatus
>
> vs
>
> 	touch Makefile
> 	git status
>
> Notice how the "runstatus" one claims that Makefile is "modified:". That's 
> exactly because it doesn't do the index refresh.

Running refresh internally in runstatus without writing the
result out _might_ be an option, but that would largely be
a hack to only help qgit.

Other shapes of "git status", such as "git status <filename>"
and "git status -a", still need to perform the same index
manipulation as "git commit" with the same parameters before
calling git-runstatus, and at that point the extra "internal
refresh" in runstatus is an unwelcome extra cycle.