Fix long-standing excessive file merges Since switching to the multihead approach, we've been creating excessive file-level merges where files are marked as merged with their ancestors. This explicitly checks at commit time whether the two parent versions are linearly related, and if so, reduces the file check-in to a non-merge. Then the file is compared against the remaining parent, and, if equal, skips check-in of that file (as it's not changed). Since we're not checking in all files that were different between versions, we no longer need to mark so many files for merge. This removes most of the 'm' state marking as well. Finally, it is possible to do a tree-level merge with no file-level changes. This will happen if one user changes file A and another changes file B. Thus, if we have have two parents, we allow commit to proceed even if there are no file-level changes.

     1

#!/bin/sh

     2

     3

# No local source

     4

hg clone a b

     5

echo $?

     6

     7

# No remote source

     8

hg clone http://127.0.0.1:3121/a b

     9

echo $?

    10

rm -rf b # work around bug with http clone

    11

    12

# Inaccessible source

    13

mkdir a

    14

chmod 000 a

    15

hg clone a b

    16

echo $?

    17

    18

# Inaccessible destination

    19

mkdir b

    20

cd b

    21

hg init

    22

hg clone . ../a

    23

echo $?

    24

cd ..

    25

chmod 700 a

    26

rm -rf a b

    27

    28

# Source of wrong type

    29

mkfifo a

    30

hg clone a b

    31

echo $?

    32

rm a

    33

    34

# Default destination, same directory

    35

mkdir q

    36

cd q

    37

hg init

    38

cd ..

    39

hg clone q

    40

    41

true