git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: inotify support, nearly there

From
Ronnie Sahlberg <sahlberg@google.com>
Date
Jul 22, 2014, 16:39 UTC
Message-ID
<CAL=YDWk90x0XBjj7rkSaeTZ-pwSj=vktvOYbyivpqqwJVAGMRw@mail.gmail.com>
In-Reply-To
<loom.20140721T070730-175@post.gmane.org>
On Sun, Jul 20, 2014 at 10:10 PM, Juan P <juandavid1707@gmail.com> wrote:
Show 20 quoted lines
> Duy Nguyen <pclouds <at> gmail.com> writes:
>
>>
>> Just a quick update for the enthusiasts. My branch file-watcher [1]
>> has got working per-user inotify support. It's a 20 patch series so
>> I'll refrain from spamming git <at> vger for a while, even though it hurts
>> your eyes a lot less than what I have posted so far. The test suite
>> ran fine with it so it's not that buggy. It has new tests too, even
>> though real inotify is not tested in the new tests. Documentation is
>> there, either in .txt or comments. Using it is simple:
>>
>> $ mkdir ~/.watcher
>> $ git file-watcher --detach ~/.watcher
>> $ git config --global filewatcher.path $HOME/.watcher
>>
>
> Will this mean that Git would work faster with repositories with large
> number of files or commits? I am new into this topic, but I am trying to
> understand, any pointers are appreciated.
>

That is the idea. Instead of having to recursively lstat() every file to find which ones have changed this will allow to query a database for "tell me all files that match this criteria xyz" which could speed up many things.

Duy, keep up the good work. Once you are ready I am more than happy to help out reviewing the patches.

regards ronnie sahlberg

Previous: Juan PNext: Duy Nguyen
Message 5 of 6 in “inotify support, nearly there”
  1. Duy NguyenJan 29, 2014
  2. Mike HommeyJan 29, 2014
  3. Duy NguyenJan 29, 2014
  4. Juan PJul 21, 2014
  5. Ronnie SahlbergJul 22, 2014
  6. Duy NguyenJul 22, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.