<div class="gmail_quote">On Sun, Jun 21, 2009 at 9:09 PM, Martin Pool <<a href="mailto:mbp@sourcefrog.net">mbp@sourcefrog.net</a>> wrote: <div> <clip> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> In theory the OS would eventually notice that the remote host is not reachable or no longer responding, but this doesn't always work in practice on all networks, and the default timeout is very long (maybe 2 hours?) -- Martin <<a href="http://launchpad.net/%7Embp/" target="_blank">http://launchpad.net/~mbp/</a>> </blockquote></div> I think you're expressing a preference for making bzr master of its own fate (as much as possible) instead of relying on low-level timeouts in the OS or libraries. I also think that's a good idea. Even in cases which do not permit this, a note in the source (not even in the dev docs) might save someone a bunch of time rediscovering it. This might be especially important if the timeout is very long. Some of the timeouts provided by windows appear to be at least as long as a typical login session. :) -M