Differences between revisions 3 and 4
Revision 3 as of 2007-06-05 19:47:44
Size: 1102
Editor: BrendanCully
Comment: Flesh out inotify instructions a bit
Revision 4 as of 2007-06-06 18:42:29
Size: 1212
Editor: BrendanCully
Comment: Add link to crew with patches applied
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
It is not yet a standalone extension. You will have to apply the patch queue to a mercurial tree and use that version of mercurial. It is not yet a standalone extension. You will have to apply the patch queue to a mercurial tree and use that version of mercurial. A recent version of crew with the patches applied may be found here: [http://hg.kublai.com/mercurial/inotify]

Inotify Extension

This extension is not distributed with Mercurial.

Author: Bryan O'Sullivan

Download site: [http://hg.kublai.com/mercurial/patches/inotify]

It is not yet a standalone extension. You will have to apply the patch queue to a mercurial tree and use that version of mercurial. A recent version of crew with the patches applied may be found here: [http://hg.kublai.com/mercurial/inotify]

It also requires Bryan's [http://hg.kublai.com/python/inotify python bindings for inotify].

Overview

This extension uses the linux 2.6 inotify API to make status instantaneous for even very large repositories, by subscribing to the paths in the repository instead of having to check them all at every status command.

Configuration

Configure your .hgrc to enable the extension by adding following lines:

[extensions]
inotify=/path/to/inotify

You can either start up the inotify extension on a repository with hg inserve or have it autostart with the following .hgrc snippet (either global or in the repository .hg/hgrc in which you would like to use inotify:

[inotify]
autostart = true


CategoryExtension

InotifyExtension (last edited 2014-03-24 01:53:35 by Rain)