From: "Shawn O. Pearce" <spearce@spearce.org>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: What's new in git-gui.git
Date: Tue, 29 May 2007 22:34:19 -0400 [thread overview]
Message-ID: <20070530023419.GK7044@spearce.org> (raw)
In-Reply-To: <20070529111836.GW4489@pasky.or.cz>
Petr Baudis <pasky@suse.cz> wrote:
> On Tue, May 29, 2007 at 06:11:08AM CEST, 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.
>
> How well does this play with NFS? I'm working at two places and at both
> have my ~ on NFS and sometimes touch the working tree from various
> machines. Would the inotify-based approach silently fail here? Or does
> inotify just refuse to work on NFS? Quick google search suggests the
> former, which is more than ok for informative purposes but big problem
> if you actually _rely_ on the inotify to keep your index up-to-date.
>From what I've read on it thus far (which isn't much) inotify
doesn't work over NFS.
I would *never* suggest relying on inotify for everything.
But making it an option for folks who can use it may be nice.
A lot of us do work on a local filesystem. Being able to get
faster status output in those cases could be nice, especially on
a big tree and slow VFS systems like Windows.
--
Shawn.
next prev parent reply other threads:[~2007-05-30 2:34 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
2007-05-29 11:18 ` Petr Baudis
2007-05-30 2:34 ` Shawn O. Pearce [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070530023419.GK7044@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).