push-and-updating to a new directory fails to update

[bwinton]

I created a new branch on my work computer, and tried to push-and-update it to a new directory at home with this command:
bzr push-and-update sftp://user@host/~/bzr/new_dir
I got the following message:
Updating location: sftp://user@host/~/bzr/new_dir
Pushed 1 revisions (1 mainline) to revno 1
No working tree to update at sftp://user@host/~/bzr/new_dir/

And when I sshed home, I saw the branch, but none of the contents.

[John A Meinel (jameinel)]

well, it is called 'push-and-update' not 'push-and-checkout'

But point taken

[John A Meinel (jameinel)]

Just to elaborate a bit further...

The original point of this command was that it could (someday) completely override 'push' so that just doing 'bzr push' would auto-update a remote WT if one was present.

I feel that there are good reasons that the current 'bzr push' *doesn't* create a remote working tree. So I don't think that 'bzr push' should always create one (which is what would happen if you changed 'push-and-update' to always create one and renamed 'push-and-update' => 'push').

The current plan is actually to change push-and-update so that it uses the Branch.hooks system to notice when you update a remote branch (sftp/bzr+ssh), and then checks if there is a remote working tree there, and then spawns a 'ssh remote bzr update'.

This would allow a plain 'bzr push' to update when reasonable, which seemed pretty slick.

It would still mean that we don't create a remote working tree.

Maybe the plugin could provide "bzr checkout-remotely" ?