##// END OF EJS Templates
patch: support diff data loss detection and upgrade...
patch: support diff data loss detection and upgrade In worst case, generating diff in upgrade mode can be two times more expensive than generating it in git mode directly: we may have to regenerate the whole diff again whenever a git feature is detected. Also, the first diff attempt is completely buffered instead of being streamed. That said, even without having profiled it yet, I am convinced we can fast-path the upgrade mode if necessary were it to be used in regular diff commands, and not only in mq where avoiding data loss is worth the price.

File last commit:

r9859:951ec6c7 default
r10189:e451e599 default
Show More
test-inotify-dirty-dirstate.out
14 lines | 343 B | text/plain | TextLexer
/ tests / test-inotify-dirty-dirstate.out
Nicolas Dumazet
inotify: Do not access inotify when dirstate is dirty (issue1811)...
r9855 % issue1810: inotify and fetch
adding foo
Benoit Boissinot
inotify: workaround test-inotify-dirty-dirstate failures...
r9859 updating to branch default
Nicolas Dumazet
inotify: Do not access inotify when dirstate is dirty (issue1811)...
r9855 1 files updated, 0 files merged, 0 files removed, 0 files unresolved
adding bar
adding spam
% issue1719: inotify and mq
% inserve
popping test.patch
patch queue now empty
% st should not output anything
applying test.patch
now at: test.patch
% st should not output anything