Re: [PATCH v2 0/6] Fast git status via a file system watcher
- From
Christian Couder <christian.couder@gmail.com>
- Date
- May 24, 2017, 10:54 UTC
- Message-ID
- <CAP8UFD20gvTZqCOcpd1iozNDHOZR1sUKRwi062wL52FNHWNC3w@mail.gmail.com>
- In-Reply-To
- <20170518201333.13088-1-benpeart@microsoft.com>
Show 7 quoted lines
> 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?
Show 9 quoted lines
> 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.