[Bug 5849] New: Failed clone/push to remote leaves unexpected empty repo

[mercurial-bugs at mercurial-scm.org]

https://bz.mercurial-scm.org/show_bug.cgi?id=5849

            Bug ID: 5849
           Summary: Failed clone/push to remote leaves unexpected empty
                    repo
           Product: Mercurial
           Version: 4.5.2
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: bug
          Priority: wish
         Component: Mercurial
          Assignee: bugzilla at mercurial-scm.org
          Reporter: zash at zash.se
                CC: mercurial-devel at mercurial-scm.org

In case `hg clone . ssh://remote/repo` is interrupted by a failure, the newly
created repo is left behind. Retrying the clone command fails because the repo
exists.

This behavior is unexpected as it differs from cloning to a local destination,
where the target repo is removed in case of interruption.

Noticed when the destination server had run out of space in /tmp, aborting
with:
remote: abort: No space left on device

-- 
You are receiving this mail because:
You are on the CC list for the bug.