From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
Michael Haggerty <mhagger@alum.mit.edu>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
David Turner <novalis@novalis.org>,
Ben Peart <peartben@gmail.com>, Joey Hess <joey@kitenet.net>,
Lars Schneider <larsxschneider@gmail.com>,
Ronnie Sahlberg <rsahlberg@google.com>,
David Turner <dturner@twopensource.com>
Subject: Re: Plugin mechanism(s) for Git?
Date: Fri, 15 Jul 2016 09:32:08 -0400 [thread overview]
Message-ID: <20160715133208.GA22711@sigill.intra.peff.net> (raw)
In-Reply-To: <CACBZZX4TA0Ljf2aNZtZ5Sj8fFj-vhoLKq5RP5YbKSS9o9Ljg+A@mail.gmail.com>
On Fri, Jul 15, 2016 at 02:46:28PM +0200, Ævar Arnfjörð Bjarmason wrote:
> On Fri, Jul 15, 2016 at 2:18 PM, Jeff King <peff@peff.net> wrote:
> > Some features, like the index-helper, aren't quite so easy. One reason
> > is that its data needs to persist as a cache between multiple git
> > invocations. In general, I think it would be nice to solve that by
> > communicating via on-disk files, rather than a running daemon (just
> > because it has fewer moving parts). But that's only half of it for
> > index-helper. It needs to monitor inotify while git isn't running at
> > all; so it really _does_ need some kind of long-running daemon.
>
> This *may* have changed in the recent versions of the series, but I'm
> fairly sure and for what it's worth to this discussion, that's not
> what the index-helper does. It's there to keep the index file in
> memory instead of reading it from disk.
>
> It can *also* if you "git update-index --watchman" spawn a watchman
> daemon in the background, which is the thing that'll be doing the
> inotify calls and needs to stay persistent, the index-helper then
> communicates with the watchman daemon "what changed since X?" to
> compute a new index when requested.
Ah, yeah, you're right. Sorry for the confusion; I haven't actually
followed the topic all that closely.
-Peff
next prev parent reply other threads:[~2016-07-15 13:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 6:46 Plugin mechanism(s) for Git? Christian Couder
2016-07-15 7:37 ` Lars Schneider
2016-07-15 16:18 ` Ben Peart
2016-07-15 16:47 ` Konstantin Khomoutov
2016-07-15 21:28 ` Eric Wong
2016-07-16 5:31 ` Duy Nguyen
2016-07-16 8:06 ` Jeff King
2016-07-15 8:04 ` Mike Hommey
2016-07-15 8:28 ` Junio C Hamano
2016-07-15 12:18 ` Jeff King
2016-07-15 12:46 ` Ævar Arnfjörð Bjarmason
2016-07-15 13:32 ` Jeff King [this message]
2016-07-15 15:52 ` Ben Peart
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=20160715133208.GA22711@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joey@kitenet.net \
--cc=larsxschneider@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=novalis@novalis.org \
--cc=pclouds@gmail.com \
--cc=peartben@gmail.com \
--cc=rsahlberg@google.com \
/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 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 NNTP newsgroup(s).