If the user attaches the output of "bzr send" rather than a plain patch, then a lot of this becomes much easier to implement. Perhaps it should be possible to "bzr send" direct to a Launchpad bug report?
Personally, I think that the automatically generated branches should be owned by the user that uploaded the patch, rather than by a robot account like "launchpad-bugger". I'm sure the Launchpad Code guys can think of a better way to give short URLs to patches on bugs, either way the branch/merge request would be be visible at code.lp.n/proj.
(Also, "bugger" is a somewhat unfortunate choice of word, at least in Australia)
If the user attaches the output of "bzr send" rather than a plain patch, then a lot of this becomes much easier to implement. Perhaps it should be possible to "bzr send" direct to a Launchpad bug report?
Personally, I think that the automatically generated branches should be owned by the user that uploaded the patch, rather than by a robot account like "launchpad-bugger". I'm sure the Launchpad Code guys can think of a better way to give short URLs to patches on bugs, either way the branch/merge request would be be visible at code.lp.n/proj.
(Also, "bugger" is a somewhat unfortunate choice of word, at least in Australia)