# HG changeset patch # User Dan Villiom Podlaski Christiansen # Date 1288486712 18000 # Node ID fdb338266705734d0b7c31213e5621be2d7bc65c # Parent c2b9e08ecf1054a196f21fdd810b57ab214b0e47 help topic: mention how "hg clone" can delete stuff. This quip was requested by Steve Borho. diff --git a/hgsubversion/help/subversion.rst b/hgsubversion/help/subversion.rst --- a/hgsubversion/help/subversion.rst +++ b/hgsubversion/help/subversion.rst @@ -139,6 +139,12 @@ leaks appear to be persistent and unavoi using the new experimental Subvertpy bindings leaks have only been observed accessing FSFS repositories over the file protocol. +Should the initial clone fail with an error, Mercurial will delete the entire +repository, including any revisions successfully converted. This can be +particularly undesirable for long-running clones. In these cases, we suggest +using the ``-r/--rev`` option to only clone a few revisions initially. After +that, an ``hg pull`` in the cloned repository will be perfectly safe. + It is not possible to interact with more than one Subversion repository per Mercurial clone. Please note that this also applies to more than one path within a repository.