Re: What's cooking in git.git (topics)

From: Marco Costalba <mcostalba@gmail.com>
Date: Mar 4, 2007, 12:40 UTC
Message-ID: <e5bfff550703040440q45b58e63pb24f17e4a1b10e31@mail.gmail.com>
In-Reply-To: <7v7itx5mep.fsf@assigned-by-dhcp.cox.net>

On 3/4/07, Junio C Hamano <junkio@cox.net> wrote:

Show 10 quoted lines

>
> * jc/status (Thu Feb 22 02:07:56 2007 -0800) 2 commits
>  - git-status: use in-core --refresh in a read-only repository.
>  - git-runstatus --refresh
>
> These two were done for the specific purpose of helping qgit,
> but I haven't heard about them, so they are on hold.  If they
> are not needed by qgit nor people who like to run git-status in
> a read-only repository, I do not see any reason to keep them.
>

Currently they are not needed by qgit. Probably neither in the future. It is better to keep working dir view disabled if in a read-only repo then wait for a sloooow command to return incorrect data (BTW _all_ repo files are always marked as 'modified' due to an issue with different implementations of lstat in cygwin and ntfs kernel driver).