> The bzr guys are probably working with a single computer, surely a laptop.
:-)
Not really, but anyway.
If you can't commit to *a* branch, why not commit to *another* *private* branch, enjoying the comfort of a real branch and, when you're ready, merge back in your integration branch and push to the public one from there ?
bzr provides many ways to work with dumb servers with *branches*. Handling working trees on such servers is not going to happen anytime soon if only because dumb *protocols* doesn't provide enough support for that.
And since *some* computer need to provide access to both sides (home/office) to allow sharing, you'd get more support from bzr by using branches on that computer.
> The bzr guys are probably working with a single computer, surely a laptop.
:-)
Not really, but anyway.
If you can't commit to *a* branch, why not commit to *another* *private* branch, enjoying the comfort of a real branch and, when you're ready, merge back in your integration branch and push to the public one from there ?
bzr provides many ways to work with dumb servers with *branches*. Handling working trees on such servers is not going to happen anytime soon if only because dumb *protocols* doesn't provide enough support for that.
And since *some* computer need to provide access to both sides (home/office) to allow sharing, you'd get more support from bzr by using branches on that computer.