Dealing with broken connections
bboissin at gmail.com
Fri Mar 14 08:43:16 CDT 2008
On Fri, Mar 14, 2008 at 10:50 AM, Guido Ostkamp <hg at ostkamp.fastmail.fm> wrote:
> I would like to know how stable Mercurial is when it comes
> deal with broken connections.
> When I do a clone of a very large remote repository and
> the connection breaks in between and I have to kill
> the Mercurial process which got stuck, what happens?
It removes the repository.
> Am I left with a broken repository?
It doesn't leave anything.
> Can I somehow resume the cloning, for example by using
> 'hg pull' instead of 'hg clone' to retrieve the rest of it?
No, but what you can do for unreliable connections is to provide a
bundle (the full history in one file)
that you can get via rsync or http.
> What, if I have worked on a repo, then tried to update it
> using 'pull' from upstream to fetch the latest changes,
> and this pull fails in between due to broken connection?
The repo will rollback and you'll get the same state as before the pull.
More information about the Mercurial