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

["Marco Costalba" <mcostalba@gmail.com>]

On 2/10/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> 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.
> > >
> > > 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.
>
> Which issues? That the lstat data are not equal on Cygwin and Linux? The
> patch does not help here.

Well, I tested the patch and indeed it helps a lot ;-)

It's correct that checking Linux lstat against cygwin one (stored in
index) gives different results, but it's now where the patch makes the
difference rechecking all the files (in memory) to see if are really
changed and discarding false positives created by lstat issues.

> Maybe a patch to Linux' ntfs driver
> would, but I fail to see how Git could possibly help here.

>
> You need a new version of _Git_ if you use that option.
>

That's a true point. Altough if git 1.5 ships _without_ '--refresh'
option in 'git runstatus' for a porcelain tool point of view it means
*do forget* that option until next major release. There's no point in
adding the feature one day after git 1.5 is out; qgit will not use
that feature anyway for next months.


   Marco