All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: What's new in git-gui.git
Date: Tue, 29 May 2007 22:39:33 -0400	[thread overview]
Message-ID: <20070530023933.GL7044@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705291157540.4648@racer.site>

Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 
> 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.

  reply	other threads:[~2007-05-30  2:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28 22:49 What's new in git-gui.git Shawn O. Pearce
2007-05-29  4:11 ` Shawn O. Pearce
2007-05-29  8:12   ` Alex Riesen
2007-05-29 10:59   ` Johannes Schindelin
2007-05-30  2:39     ` Shawn O. Pearce [this message]
2007-05-29 11:18   ` Petr Baudis
2007-05-30  2:34     ` Shawn O. Pearce
2007-05-29  7:46 ` Johannes Sixt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070530023933.GL7044@spearce.org \
    --to=spearce@spearce.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.