##// END OF EJS Templates
upstream » mercurial-mirror
RSS

Clone from https://www.mercurial-scm.org/repo/hg-all

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.
Augie Fackler - - Load All Authors

File last commit:

r10178:cd477be6 default
r10189:e451e599 default
Show More
test-subrepo-svn.out
48 lines | 1011 B | text/plain | TextLexer
/ tests / test-subrepo-svn.out
History | Source | Raw |Copy content |Copy permalink
Augie Fackler
subrepo: Subversion support
 r10178 % create subversion repo
Checked out revision 0.
A alpha
Adding alpha
Transmitting file data .
Committed revision 1.
% create hg repo
% first revision, no sub
adding a
% add first svn sub
committing subrepository s
% debugsub
path s
source file:///root/svn-repo
revision 1
% change file in svn and hg, commit
committing subrepository s
Sending s/alpha
Transmitting file data .
Committed revision 2.
At revision 2.
path s
source file:///root/svn-repo
revision 2
% should be empty despite change to s/a
% add a commit from svn
U alpha
Updated to revision 2.
Sending alpha
Transmitting file data .
Committed revision 3.
% this commit from hg will fail
committing subrepository s
abort: svn: Commit failed (details follow):
svn: File '/alpha' is out of date
% clone
updating to branch default
A s/alpha
Checked out revision 2.
3 files updated, 0 files merged, 0 files removed, 0 files unresolved
% debugsub in clone
path s
source file:///root/svn-repo
revision 2