bzr-email should support email on push

[Steve Langasek]

bzr-email only sends mail on commit, not on push. But there are many occasions where the 'push' is the only time that mail should be generated; for instance, if I have a local branch on my machine which I periodically push to a public branch hosted on a central server, I want to let users know about the contents of whatever I'm pushing to that server - not necessarily the individual commits that I make locally.

If configured correctly this shouldn't generate spurious emails, because I would only enable bzr-email for the bzr+ssh uri, not for the local one.

[John A Meinel (jameinel)]

This something that should probably be discussed as a feature discussion, more than a bug report.
Care to discuss it on <email address hidden>?

Also, how would you want the emails to be generated? One email per commit, or just one summary email?

If one email per commit, how do you handle merged revisions. Do you describe each separately, or just how we do it now?

I believe it wouldn't be hard to implement it, but the overall design should probably be worked out first.

[Dimitri John Ledkov (xnox)]

@bzr-builddeb subscribers

This is already implemented as part of the lp:bzr-email plugin. Maintainer just has to set it up correctly =) see Bug #250934. And it's upto maintainer to decide what she is committing where. Cause I maintain my packages both in Debian/Launchpad from the same tree and some commits are not meant for the other ;-)

You can also set up this hook to run on alioth using just /usr/bin/mail so the config is really three lines for the branch then =) to, from & public branch url.

I will write up documentation on Alioth/Bzr wiki about this =)