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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Sat, 10 Feb 2007, Marco Costalba wrote:

> On 2/10/07, Johannes Schindelin <Johannes.Schindelin@xxxxxx> 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. Maybe a patch to Linux' ntfs driver 
would, but I fail to see how Git could possibly help here.

If git-diff is trying to write files, _that_ would be a bug.

As for your use of git-status: I think it is wrong. You said you want to 
check if the working directory is clean. Then just do that, and do not try 
to generate the message meant for editing the commit message.

> > 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.

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

And if you can do without depending on a newer Git, it is _bad_ to do it 
nevertheless.

Ciao,
Dscho

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]