Submit by mail

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hermann Kraus wrote:
> To store the configuration data I want to add to new files to the .bzr  
> directory:
> x-submit-addressStores the default email address (similar to x-pull,  
> x-push-data)

I'd prefer for configuration data to be stored in .bzr/branch/branch.conf

In any case, only plugins should use the x- prefix.

> x-submit-message  Stores a message that is shown before one can send a  
> mail (can
> be disabled by the user) that contains information about what mailinglist  
> the
> message is going to, where to subscribe, special format requirements, etc.

This doesn't sound like a feature I would want to use, or to have used
against me.

>  From the original proposal: "To allow bzr branch to know how to set the  
> submit
> target, there should be a file in the .bzr/ directory indicating the  
> target. To
> allow for a different target for people who branch from me, versus my  
> default
> branch target, there should be 2 files. (.bzr/submit-to and  
> .bzr/children-submit-
> to) bzr branch should be smart, such that when it creates a branch, it  
> will use
>   .bzr/children-submit-to if it is available."
> 
> I can't see how this would be useful, but if someone can tell me a  
> situation where
> this makes sense I'll try my best to add it.

As the leader of a project, I may submit my changes to one place, but
want others to submit their patches to me.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEjF2/0F+nu1YWqI0RAkv2AJwNL4BR4b0bx842hrOLfmKMd82nJACdFWb1
eVVT0cic6NgOo9hgQT2dtrc=
=Q7ge
-----END PGP SIGNATURE-----