Launchpad Entry: https://launchpad.net/products/bzr/+spec/SubmitByMail
PQM provides a way to submit merge requests by email and have them automatically applied. It might be nice if this were smoothly integrated with bzr.
Erik Bågfors <email@example.com> to mbp, Bazaar-NG How about adding this kind of functionality into bzr itself? Look at how darcs handles it. It's one if the nicest things about darcs. a darcs "server" can simply be a mail address you mail to, that runs all mails trough pgp and then applies them if they match (you can add tests as well by just adding "apply test" to the repo config file). for example a procmail can look like this :0: * ^TOmy darcs repo |(umask 022; darcs apply --reply firstname.lastname@example.org \ --repodir /path/to/your/repo --verify /path/to/the/allowed_keys) That's a dead simple way to set up a "server" for trusted people to submit to. I don't know how pqm works and it might be lot's better, but having this functionality built into bzr has lot's of advantages I think.
This has the big advantage that no special kind of server is required. A procmail rule is something almost anyone can set up, including on a desktop/firewalled/not-permanently-connected machine.
It would be nice to send the changes as a series of bzr changesets (as mentionned on BzrWishlist).
There should be one command to send the changeset (bzr send, bzr submit ?), and one to apply the changeset, to be called manually or from a procmail rule.
It is important that the description section covers the functionality-related aspects (the "what") of the change. Providing rationale (the "why") is always a plus.
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
Should cover changes required to the UI, or specific UI that is required to implement this
Code changes should include an overview of what needs to change, and in some cases even the specific details.
This section should house the larger issues that need discussing; you can sprinkle XXXs around the page if you want to keep the smaller open issues in context.