[ I'm Cc-ing bzr's mailing list to get more opinions. ] "Daniel 'NebuchadnezzaR' Dehennin" <[EMAIL PROTECTED]> writes:
> Le 4693 Septembre 1993, Matthieu Moy a tapoté: >> Notes : >> >> 1) I used Robert's email sending plugin to send this message. I had to >> patch it a bit (for example, to show the actual URL of my branch >> instead of a private URL used for uploading), but it works well >> now. http://bazaar-vcs.org/PluginRegistry for the interested. > > Can it be better to include the URL in the body of the mail ? Indeed, this is how I would have done it too, but I kept this as it was. Perhaps just the branch nick could be in the subject line, and the URL in the body. I'd see something like that: ,---- | Subject: Rev 37: Updated .bzrignore (new bzr have no default ignore). in dvc.moy | | New revision in http://www-verimag.imag.fr/~moy/bzr/dvc/moy/ | ------------------------------------------------------------ | revno: 37 | revision-id: [EMAIL PROTECTED] | parent: [EMAIL PROTECTED] | committer: Matthieu Moy <[EMAIL PROTECTED]> | branch nick: dvc.moy | timestamp: Sat 2006-07-08 15:18:41 +0200 | message: | Updated .bzrignore (new bzr have no default ignore). | modified: | .bzrignore | bzrignore-20060701105852-er2escjfqktvi63g-1 `---- Indeed, I was wondering whether it was best to 1) provide an easy way for the user to specify the format of the email to send. For example, a ~/.bzr-email file saying stg like ,---- | Subject: @revno@: @summary@ in @url@ | | @log@ `---- and have the email plugin do variable substitution to send the actual mail. 2) find a format that would suite everyone. Indeed, 1) seems interesting, but an advantage of 2) is that a common format helps in having automated tools on the recipient side (we already have something for tla + DVC + Gnus, to view the diff or perform a merge easily while reading this sort of messages, it would be cool to have it for bzr too). 1) is also perhaps a bit overengineered. Perhaps it's: 3) allow 1), but with a default corresponding to 2). -- Matthieu _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
