Fix hg clone race with writer Most read operations in hg don't need locks because we order reads and writes for consistency. Clone is an exception to this as we're copying entire file histories and could end up with more file history copied than we have commits. For now, make clone take a lock on the source repo. Non-hardlinked clone should eventually be changed to use lockless pull.

     1

#!/bin/sh -e

     2

     3

umask 027

     4

mkdir test1

     5

cd test1

     6

     7

hg init

     8

touch a b

     9

hg add a b

    10

hg ci -m "added a b" -d "0 0"

    11

    12

cd ..

    13

mkdir test2

    14

cd test2

    15

    16

hg init

    17

hg pull ../test1

    18

hg co

    19

chmod +x a

    20

hg ci -m "chmod +x a" -d "0 0"

    21

    22

cd ../test1

    23

echo 123 >>a

    24

hg ci -m "a updated" -d "0 0"

    25

    26

hg pull ../test2

    27

hg heads

    28

hg history

    29

    30

hg -v co -m

    31

    32

ls -l ../test[12]/a > foo

    33

cut -b 0-10 < foo

    34