We would also have use for something like this, with, it sounds like, slightly different needs from the original requester. We have developers who work on a development server via SSH, and work on bzr checkouts that, from the development server context, are local (e.g., a checkout from /bzr/someproject/trunk to /home/some_developer/projects/someproject on the same machine), and they do commits, updates, etc., via SSH terminal at the moment, so for us, the optimal integration with RSE would be if the plugin could actually use the remote bzr executable and do everything remotely, rather than use a local executable and do things via bzr+ssh. No sense in downloading all of data necessary for a commit so the local bzr can process it, only to upload it again at commit time.
We would also have use for something like this, with, it sounds like, slightly different needs from the original requester. We have developers who work on a development server via SSH, and work on bzr checkouts that, from the development server context, are local (e.g., a checkout from /bzr/someprojec t/trunk to /home/some_ developer/ projects/ someproject on the same machine), and they do commits, updates, etc., via SSH terminal at the moment, so for us, the optimal integration with RSE would be if the plugin could actually use the remote bzr executable and do everything remotely, rather than use a local executable and do things via bzr+ssh. No sense in downloading all of data necessary for a commit so the local bzr can process it, only to upload it again at commit time.