Skip to content
Snippets Groups Projects
  • Dan Villiom Podlaski Christiansen's avatar
    bf9084d8
    clone: always use a single transaction · bf9084d8
    Dan Villiom Podlaski Christiansen authored
    Given that Mercurial will delete the repository on any error, using
    anything more than a single transaction is a waste of resources. In
    fact, the only way to “recover” a partial clone using hg-git is to
    forcibly KILL the process. This makes us match the behaviour of
    Mercurial: clone isn't resumable, period, and not even inspecting the
    repository during the clone suggests otherwise.
    
    This currently doesn't affect the current defaults, though, which are to
    always use a single transaction.
    bf9084d8
    History
    clone: always use a single transaction
    Dan Villiom Podlaski Christiansen authored
    Given that Mercurial will delete the repository on any error, using
    anything more than a single transaction is a waste of resources. In
    fact, the only way to “recover” a partial clone using hg-git is to
    forcibly KILL the process. This makes us match the behaviour of
    Mercurial: clone isn't resumable, period, and not even inspecting the
    repository during the clone suggests otherwise.
    
    This currently doesn't affect the current defaults, though, which are to
    always use a single transaction.
git_handler.py 75.83 KiB