extend network protocol to stop clients from locking servers now all repositories have capabilities slot, tuple with list of names. if 'unbundle' capability present, repo supports push where client does not need to lock server. repository classes that have unbundle capability also have unbundle method. implemented for ssh now, will be base for push over http. unbundle protocol acts this way. server tells client what heads it has during normal negotiate step. client starts unbundle by repeat server's heads back to it. if server has new heads, abort immediately. otherwise, transfer changes to server. once data transferred, server locks and checks heads again. if heads same, changes can be added. else someone else added heads, and server aborts. if client wants to force server to add heads, sends special heads list of 'force'.

     1

pulling from ../a

     2

searching for changes

     3

abort: repository is unrelated

     4

pulling from ../a

     5

searching for changes

     6

warning: repository is unrelated

     7

adding changesets

     8

adding manifests

     9

adding file changes

    10

added 1 changesets with 1 changes to 1 files (+1 heads)

    11

(run 'hg heads' to see heads, 'hg merge' to merge)

    12

changeset:   1:bdcee5d51fa6

    13

tag:         tip

    14

user:        a

    15

date:        Mon Jan 12 13:46:40 1970 +0000

    16

summary:     a

    17

    18

changeset:   0:f155ba1aa5ba

    19

user:        b

    20

date:        Mon Jan 12 13:46:40 1970 +0000

    21

summary:     b

    22