Mercurial > hgsubversion
changeset 736:fdb338266705
help topic: mention how "hg clone" can delete stuff.
This quip was requested by Steve Borho.
| author | Dan Villiom Podlaski Christiansen <danchr@gmail.com> |
|---|---|
| date | Sat, 30 Oct 2010 19:58:32 -0500 |
| parents | c2b9e08ecf10 |
| children | 708234ad6c97 |
| files | hgsubversion/help/subversion.rst |
| diffstat | 1 files changed, 6 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- 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.