From: Christian Couder <christian.couder@gmail.com>
To: Ben Peart <peartben@gmail.com>
Cc: git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
Ben Peart <benpeart@microsoft.com>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
David Turner <David.Turner@twosigma.com>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH v2 0/6] Fast git status via a file system watcher
Date: Wed, 24 May 2017 12:54:48 +0200 [thread overview]
Message-ID: <CAP8UFD20gvTZqCOcpd1iozNDHOZR1sUKRwi062wL52FNHWNC3w@mail.gmail.com> (raw)
In-Reply-To: <20170518201333.13088-1-benpeart@microsoft.com>
> Design
> ~~~~~~
>
> A new git hook (query-fsmonitor) must exist and be enabled
> (core.fsmonitor=true) that takes a time_t formatted as a string and
> outputs to stdout all files that have been modified since the requested
> time.
Is there a reason why there is a new hook, instead of a
"core.fsmonitorquery" config option to which you could pass whatever
command line with options?
> A new 'fsmonitor' index extension has been added to store the time the
> fsmonitor hook was last queried and a ewah bitmap of the current
> 'fsmonitor-dirty' files. Unmarked entries are 'fsmonitor-clean', marked
> entries are 'fsmonitor-dirty.'
>
> As needed, git will call the query-fsmonitor hook proc for the set of
> changes since the index was last updated. Git then uses this set of
> files along with the list saved in the fsmonitor index extension to flag
> the potentially dirty index and untracked cache entries.
So this can work only if "core.untrackedCache" is set to true?
Thanks for working on this,
Christian.
next prev parent reply other threads:[~2017-05-24 10:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 20:13 [PATCH v2 0/6] Fast git status via a file system watcher Ben Peart
2017-05-18 20:13 ` [PATCH v2 1/6] bswap: add 64 bit endianness helper get_be64 Ben Peart
2017-05-18 20:13 ` [PATCH v2 2/6] dir: make lookup_untracked() available outside of dir.c Ben Peart
2017-05-18 20:13 ` [PATCH v2 3/6] fsmonitor: teach git to optionally utilize a file system monitor to speed up detecting new or changed files Ben Peart
2017-05-19 15:33 ` Ben Peart
2017-05-20 10:41 ` Junio C Hamano
2017-05-24 12:30 ` Christian Couder
2017-05-18 20:13 ` [PATCH v2 4/6] fsmonitor: add test cases for fsmonitor extension Ben Peart
2017-05-20 16:55 ` Torsten Bögershausen
2017-05-18 20:13 ` [PATCH v2 5/6] fsmonitor: add documentation for the " Ben Peart
2017-05-20 11:28 ` Junio C Hamano
2017-05-20 12:10 ` Ævar Arnfjörð Bjarmason
2017-05-22 16:18 ` Ben Peart
2017-05-22 17:28 ` Ævar Arnfjörð Bjarmason
2017-05-25 13:49 ` Ben Peart
2017-05-18 20:13 ` [PATCH v2 6/6] fsmonitor: add a sample query-fsmonitor hook script for Watchman Ben Peart
2017-05-24 13:12 ` Christian Couder
2017-05-26 9:47 ` Ævar Arnfjörð Bjarmason
2017-05-26 16:02 ` Ben Peart
2017-05-25 21:05 ` Ævar Arnfjörð Bjarmason
2017-05-24 10:54 ` Christian Couder [this message]
2017-05-25 13:55 ` [PATCH v2 0/6] Fast git status via a file system watcher Ben Peart
2017-05-27 6:57 ` Christian Couder
2017-05-30 18:05 ` Ben Peart
2017-05-30 20:33 ` Christian Couder
2017-05-30 23:11 ` Ben Peart
2017-05-31 7:37 ` Christian Couder
2017-05-31 7:59 ` Christian Couder
2017-05-31 13:37 ` Ben Peart
2017-05-31 14:10 ` Ævar Arnfjörð Bjarmason
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=CAP8UFD20gvTZqCOcpd1iozNDHOZR1sUKRwi062wL52FNHWNC3w@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=David.Turner@twosigma.com \
--cc=benpeart@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=pclouds@gmail.com \
--cc=peartben@gmail.com \
--cc=peff@peff.net \
/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).