Re: 'git status' is not read-only fs friendly

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Feb 9, 2007, 20:59 UTC
Message-ID: <Pine.LNX.4.64.0702091253120.8424@woody.linux-foundation.org>
In-Reply-To: <e5bfff550702091235x74e44362gad5b9b6076a5ea53@mail.gmail.com>

On Fri, 9 Feb 2007, Marco Costalba wrote:

Show 5 quoted lines

> 
> If I modify qgit in running 'git runstatus' as a fallback in case 'git
> status' exits with an error (without checking what kind of error
> exactly) could be an acceptable path or could hide subtle
> side-effects? I have no the knowledge to answer this by hand.

It's probably better for you to just

 - run "git update-index --refresh" and don't care about the exit value
 - run "git runstatus" unconditionally

which should basically get you something working.

HOWEVER, it's also quite possible that "git-commit.sh" should just do this on its own. If the update-index fails, we really only care if we literally use the index later to *write* something, ie the commit case. For just "git status", maybe we should just silently ignore the error..

		Linus