tests/test-inotify-dirty-dirstate.out

inotify: Do not access inotify when dirstate is dirty (issue1811)

Original patch was provided by Simon Heimberg

It delegates dirstate computation to dirstate.status when dirstate is dirty:
better be slow from time to time instead of using wrong data.

This solves issue1719. As the last component, issue1810, is still not solved,
test-inotify-dirty-dirstate will fail for now. It emphasizes a regression due
to 7c01599dd340:

changeset:   9515:7c01599dd340
user:        Nicolas Dumazet <[e-mail]>
date:        Sun Aug 16 11:11:37 2009 +0900
summary:     inotify: use cmdutil.service instead of local daemonizing code

Ancestors of 7c01599dd30 are passing the test, when applied this patch.
Regression has to be investigated, but this patch is important since it affects
often mq operations.

% issue1810: inotify and fetch
adding foo
updating working directory
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
adding bar
adding spam
% issue1719: inotify and mq
% inserve
? hg.pid
popping test.patch
patch queue now empty
% st should not output anything
? hg.pid
applying test.patch
now at: test.patch
% st should not output anything
? hg.pid
? hg.pid