##// 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:

r6336:4b0c9c67 default
r10189:e451e599 default
Show More
test-empty-file.out
20 lines | 640 B | text/plain | TextLexer
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
created new head
changeset: 2:62ec0e86d1e5
tag: tip
parent: 0:567dde5e6e98
user: test
date: Mon Jan 12 13:46:40 1970 +0000
summary: add empty3
changeset: 1:41ab7b321727
user: test
date: Mon Jan 12 13:46:40 1970 +0000
summary: add empty2
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
(branch merge, don't forget to commit)
M empty2
b80de5d138758541c5f05265ad144ab9fa86d1db 644 empty1
b80de5d138758541c5f05265ad144ab9fa86d1db 644 empty2
b80de5d138758541c5f05265ad144ab9fa86d1db 644 empty3