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

(the addremove command is deprecated; use add and remove --after instead)

     2

adding foo

     3

checking changesets

     4

checking manifests

     5

crosschecking files in changesets and manifests

     6

checking files

     7

1 files, 1 changesets, 1 total revisions

     8

requesting all changes

     9

adding changesets

    10

adding manifests

    11

adding file changes

    12

added 1 changesets with 1 changes to 1 files

    13

1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    14

checking changesets

    15

checking manifests

    16

crosschecking files in changesets and manifests

    17

checking files

    18

1 files, 1 changesets, 1 total revisions

    19

0 files updated, 0 files merged, 0 files removed, 0 files unresolved

    20

foo

    21

2ed2a3912a0b24502043eae84ee4b279c18b90dd 644 foo

    22

pulling from http://localhost:20059/

    23

searching for changes

    24

no changes found