On Tue, 2008-04-01 at 15:18 +1300, Amos Jeffries wrote:
> I'm getting annoyed by bzr's method of handling "bzr send" emails.
>
> As you may have noticed it adds the subject of the last commit to the
> email. regardless of the message thats asked for manually during the send
> process.
>
> It would be good if bzr pulled its email subject from that new message. We
> are going to be sick of feature submissions going up as "Merged from
> trunk" because the last the thing the developer did was properly check the
> branch was up-to-date.
I think this is a good suggestion. Its a little complex because most
email clients want a subject given when starting the new email, and you
can edit the subject *and* the message at that point. Are you perhaps
supplying a fully prepared message to bzr send? If so then we should
special case that.
On Tue, 2008-04-01 at 15:18 +1300, Amos Jeffries wrote:
> I'm getting annoyed by bzr's method of handling "bzr send" emails.
>
> As you may have noticed it adds the subject of the last commit to the
> email. regardless of the message thats asked for manually during the send
> process.
>
> It would be good if bzr pulled its email subject from that new message. We
> are going to be sick of feature submissions going up as "Merged from
> trunk" because the last the thing the developer did was properly check the
> branch was up-to-date.
I think this is a good suggestion. Its a little complex because most
email clients want a subject given when starting the new email, and you
can edit the subject *and* the message at that point. Are you perhaps
supplying a fully prepared message to bzr send? If so then we should
special case that.
affects bzr
-- www.robertcolli ns.net/ keys.txt>.
GPG key available at: <http://