Mercurial > hg
view tests/blacklists/inotify-failures @ 14732:e9ed3506f066 stable
backout of d04ba50e104d: allow to qpop/push with a dirty working copy
The new behavior was breaking existing tools that relied on a sequence such as
this:
1) start with a dirty working copy
2) qimport some patch
3) try to qpush it
4) old behavior would fail at this point due to outstanding changes.
(new behavior would only fail if the outstanding changes and the patches
changes intersect)
5) innocent user qrefreshes, gets his local changes in the imported patch
It's worth considering if we can move this behavior to -f in the future.
author | Idan Kamara <idankk86@gmail.com> |
---|---|
date | Fri, 24 Jun 2011 23:25:42 +0300 |
parents | c437745f50ec |
children | 3afb61810680 |
line wrap: on
line source
# When --inotify is activated, help output and config changes: test-debugcomplete test-empty test-fncache test-globalopts test-help test-hgrc test-inherit-mode test-qrecord test-strict # --inotify activates de facto the inotify extension. It does not play well # with inotify-specific tests, which activate/desactivate inotify at will: test-inotify test-inotify-debuginotify test-inotify-dirty-dirstate test-inotify-issue1208 test-inotify-issue1371 test-inotify-issue1542 test-inotify-issue1556 test-inotify-lookup