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

From: "Marco Costalba" <mcostalba@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
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:31:37 +0100	[thread overview]
Message-ID: <e5bfff550702100631w1b6243e7i44039ceaa8d3fe93@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0702101517360.22628@wbgn013.biozentrum.uni-wuerzburg.de>

On 2/10/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> 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.
>
> So, why don't you just do a
>
>         git diff --name-only HEAD
>
> and check for an empty output???
>

It seems to have the same issues of 'git runstatus' in case of ntfs
filesystems, so I would prefer, eventually, use 'git runstatus' that
at least gives me index status of the files.

> No need for a patch to Git (so late in the -rc phase), or backwards
> incompatibility...
>

Well, it's a _new_ option so I fail to see backwards incompatibility.
Perhaps you are referring to qgit backward incompatibility, but in any
case a new version of qgit is due to fix a parsing bug that shows
after a modification of 'git rev-list' output occurred in git 1.5
development.

  Marco