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

pulling from ../a

     2

searching for changes

     3

warning: pulling from an unrelated repository!

     4

adding changesets

     5

adding manifests

     6

adding file changes

     7

added 1 changesets with 1 changes to 1 files

     8

(run 'hg update' to get a working copy)

     9

changeset:   1:9a79c33a9db3

    10

tag:         tip

    11

user:        a

    12

date:        Thu Jan  1 00:00:00 1970 +0000

    13

summary:     a

    14

    15

changeset:   0:01f8062b2de5

    16

user:        b

    17

date:        Thu Jan  1 00:00:00 1970 +0000

    18

summary:     b

    19