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

r9329:567648ea default
r10189:e451e599 default
Show More
test-clone-failure
68 lines | 1018 B | text/plain | TextLexer
#!/bin/sh
# No local source
hg clone a b
echo $?
# No remote source
hg clone http://127.0.0.1:3121/a b
echo $?
rm -rf b # work around bug with http clone
# Inaccessible source
mkdir a
chmod 000 a
hg clone a b
echo $?
# Inaccessible destination
mkdir b
cd b
hg init
hg clone . ../a
echo $?
cd ..
chmod 700 a
rm -r a b
# Source of wrong type
if "$TESTDIR/hghave" -q fifo; then
mkfifo a
hg clone a b
echo $?
rm a
else
echo "abort: repository a not found!"
echo 255
fi
# Default destination, same directory
mkdir q
cd q
hg init
cd ..
hg clone q
# destination directory not empty
mkdir a
echo stuff > a/a
hg clone q a
echo $?
# leave existing directory in place after clone failure
hg init c
cd c
echo c > c
hg commit -A -m test
chmod -rx .hg/store/data
cd ..
mkdir d
hg clone c d 2> err
echo $?
test -d d && echo "dir is still here" || echo "dir is gone"
test -d d/.hg && echo "repo is still here" || echo "repo is gone"
# reenable perm to allow deletion
chmod +rx c/.hg/store/data
true