Re: What's new in git-gui.git

From: Shawn O. Pearce <spearce@spearce.org>
Date: May 30, 2007, 02:39 UTC
Message-ID: <20070530023933.GL7044@spearce.org>
In-Reply-To: <Pine.LNX.4.64.0705291157540.4648@racer.site>

Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 9 quoted lines

> 
> On Tue, 29 May 2007, Shawn O. Pearce wrote:
> 
> > Apparently the Linux folks have this new fangled inotify thing that is 
> > also good at telling applications about changed files. It seems the hg 
> > folks are using it to speed up "hg status" by having a background daemon 
> > keep track of which files are dirty, and which aren't.
> 
> An SCM which runs a background process? Please, no.

Well, not required. Making it required to make things work is clearly insane. But letting a user optionally start a background process to monitor their working directory and cache dirty flags for files may be faster for some users on some systems and some workflows. And it could make git-gui more responsive. If git-gui starts/stops the "background process" along with its window opening/closing, who cares that its running? Especially if it can be enabled/disabled by a little checkbox thingy?

> Next thing is, you have a daemon running which permanently scans your 
> source code for copynotsoright violations.

I won't.  Maybe a future employer of yours might...  ;-)

-- 
Shawn.