Mercurial > hg
changeset 27887:a30b582b8be4
commands: document clone bundles hooks and rollback behavior
The added content is inside a verbose container.
I figure it makes sense to explicitly document behavior, including
with the caveat it may change later. People can't say they weren't
warned!
| author | Gregory Szorc <gregory.szorc@gmail.com> |
|---|---|
| date | Thu, 14 Jan 2016 21:21:59 -0800 |
| parents | 0288e63ea3be |
| children | 6c740218215d |
| files | mercurial/commands.py |
| diffstat | 1 files changed, 8 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/mercurial/commands.py Thu Jan 14 22:50:55 2016 -0800 +++ b/mercurial/commands.py Thu Jan 14 21:21:59 2016 -0800 @@ -1502,6 +1502,14 @@ h) the tipmost head of the default branch i) tip + When cloning from servers that support it, Mercurial may fetch + pre-generated data from a server-advertised URL. When this is done, + hooks operating on incoming changesets and changegroups may fire twice, + once for the bundle fetched from the URL and another for any additional + data not fetched from this URL. In addition, if an error occurs, the + repository may be rolled back to a partial clone. This behavior may + change in future releases. See :hg:`help -e clonebundles` for more. + Examples: - clone a remote repository to a new directory named hg/::