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

From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, GIT list <git@vger.kernel.org>
Subject: Re: 'git status' is not read-only fs friendly
Date: Sat, 10 Feb 2007 15:59:10 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.63.0702101554170.22628@wbgn013.biozentrum.uni-wuerzburg.de> (raw)
In-Reply-To: <e5bfff550702100648p6db5fc67vb5e4a04d40771922@mail.gmail.com>

Hi,

On Sat, 10 Feb 2007, Marco Costalba wrote:

> On 2/10/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > On Sat, 10 Feb 2007, Marco Costalba wrote:
> > > On 2/10/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > > > On Fri, 9 Feb 2007, Marco Costalba wrote:
> > > >
> > > > > I just need to know if current working directory is clean and report
> > > > > back to qgit user, so read-only access would be ok for me.
>
> [... talking about a patch to introduce --refresh to git-status ...]
>
> Well, I tested the patch and indeed it helps a lot ;-)

Not really. The thing is, git-status does a lot more than what you need. 
And what you need is _only_ what "git diff --name-only HEAD" does already!

It _also_ checks the index, it _also_ only checks the files with different 
stat information, but it does _not_ try to update the index and prepare a 
message to be displayed when committing.

So, what is the big problem about accepting that patching git-status for 
one obscure use is wrong, wrong, wrong, when git-diff already does what is 
needed???

Ciao,
Dscho