comparison mercurial/commands.py @ 37498:aacfca6f9767

wireproto: support for pullbundles Pullbundles are similar to clonebundles, but served as normal inline bundle streams. They are almost transparent to the client -- the only visible effect is that the client might get less changes than what it asked for, i.e. not all requested head revisions are provided. The client announces support for the necessary retries with the partial-pull capability. After receiving a partial bundle, it updates the set of revisions shared with the server and drops all now-known heads from the request list. It will then rerun getbundle until no changes are received or all remote heads are present. Extend badserverext to support per-socket limit, i.e. don't assume that the same limits should be applied to all sockets. Differential Revision: https://phab.mercurial-scm.org/D1856
author Joerg Sonnenberger <joerg@bec.de>
date Thu, 18 Jan 2018 12:54:01 +0100
parents d665b4ea7d4c
children 8bb3899a0f47
comparison
equal deleted inserted replaced
37497:1541e1a8e87d 37498:aacfca6f9767
1411 g) the revision marked with the '@' bookmark, if present 1411 g) the revision marked with the '@' bookmark, if present
1412 h) the tipmost head of the default branch 1412 h) the tipmost head of the default branch
1413 i) tip 1413 i) tip
1414 1414
1415 When cloning from servers that support it, Mercurial may fetch 1415 When cloning from servers that support it, Mercurial may fetch
1416 pre-generated data from a server-advertised URL. When this is done, 1416 pre-generated data from a server-advertised URL or inline from the
1417 hooks operating on incoming changesets and changegroups may fire twice, 1417 same stream. When this is done, hooks operating on incoming changesets
1418 once for the bundle fetched from the URL and another for any additional 1418 and changegroups may fire more than once, once for each pre-generated
1419 data not fetched from this URL. In addition, if an error occurs, the 1419 bundle and as well as for any additional remaining data. In addition,
1420 repository may be rolled back to a partial clone. This behavior may 1420 if an error occurs, the repository may be rolled back to a partial
1421 change in future releases. See :hg:`help -e clonebundles` for more. 1421 clone. This behavior may change in future releases.
1422 See :hg:`help -e clonebundles` for more.
1422 1423
1423 Examples: 1424 Examples:
1424 1425
1425 - clone a remote repository to a new directory named hg/:: 1426 - clone a remote repository to a new directory named hg/::
1426 1427
3950 This finds all changes from the repository at the specified path 3951 This finds all changes from the repository at the specified path
3951 or URL and adds them to a local repository (the current one unless 3952 or URL and adds them to a local repository (the current one unless
3952 -R is specified). By default, this does not update the copy of the 3953 -R is specified). By default, this does not update the copy of the
3953 project in the working directory. 3954 project in the working directory.
3954 3955
3956 When cloning from servers that support it, Mercurial may fetch
3957 pre-generated data. When this is done, hooks operating on incoming
3958 changesets and changegroups may fire more than once, once for each
3959 pre-generated bundle and as well as for any additional remaining
3960 data. See :hg:`help -e clonebundles` for more.
3961
3955 Use :hg:`incoming` if you want to see what would have been added 3962 Use :hg:`incoming` if you want to see what would have been added
3956 by a pull at the time you issued this command. If you then decide 3963 by a pull at the time you issued this command. If you then decide
3957 to add those changes to the repository, you should use :hg:`pull 3964 to add those changes to the repository, you should use :hg:`pull
3958 -r X` where ``X`` is the last changeset listed by :hg:`incoming`. 3965 -r X` where ``X`` is the last changeset listed by :hg:`incoming`.
3959 3966