I think his use case is like mine, where I want to take something I've been working on locally, and turn it into a checkout of a public branch. (newly created).
I do this when working on someone else's plugin. Or if I was working on my laptop without an internet connection.
I personally do this at the same time. So it is a single:
bzr push foo/bar
<up arrow, edit push to bind, enter>
So *my* use case would be "bzr push-and-bind", or 'bzr make-public-checkout'.
On IRC, Jeff was saying he pushes to the public location for a while, before he decides it is easier to just use a checkout.
There is a different use case which is having a checkout, that you then unbind, and then re-bind when you come online, which --dirstate-tags does handle. But I think this is separate.
I think his use case is like mine, where I want to take something I've been working on locally, and turn it into a checkout of a public branch. (newly created).
I do this when working on someone else's plugin. Or if I was working on my laptop without an internet connection.
I personally do this at the same time. So it is a single:
bzr push foo/bar
<up arrow, edit push to bind, enter>
So *my* use case would be "bzr push-and-bind", or 'bzr make-public- checkout' .
On IRC, Jeff was saying he pushes to the public location for a while, before he decides it is easier to just use a checkout.
There is a different use case which is having a checkout, that you then unbind, and then re-bind when you come online, which --dirstate-tags does handle. But I think this is separate.