Comment 8 for bug 282983

Hi Fabrice

Hmm that's no good - I'm not much help on Gentoo unfortunately. That tutorial is interesting but I found bzr push way too slow for large branches (I think it uploads the entire branch to the remote server ?).

I use bzr send instead to create a patch file, that only contains branch changes, on the remote server. As bzr send doesn't support saving directives to remote paths (https://bugs.launchpad.net/bzr/+bug/221021) the patch file is uploaded using a pipe that cat's the file into the remote location:

//cd into local branch (made with bzr branch sftp://me@server/path/to/remote/branch)
//hack away and commit
$ bzr send -v -o - sftp://me@server/path/to/remote/branch | ssh me@server "cat >/path/to/directives/my-directive.patch"

Obviously having your public ssh key on the remote server helps with password prompting.

With this in place, I have a directive stored on the remote server, and we have a history of all directives applied to the remote branches. Our patch manager can review the directives prior to them being merged into production code and reject that ones that contain incorrect/invalid code. Hope that helps ?

Cheers
James