[PATCH] patchbomb: allow multiple addresses in a single --to/cc/bcc argument

Sune Foldager cryo at cyanite.org
Sun Nov 1 09:24:15 CST 2009


Marti Raudsepp wrote:
> On Sun, Nov 1, 2009 at 11:12 AM, Sune Foldager <cryo at cyanite.org> wrote:
>> [...] I still find the feature a bit weird. I mean, then we should also
>> change other commands which take multiple arguments to accept comma
>> separated lists? Or is this because the configuration is done with
>> commas (due to the way the config format works, I guess)?
> 
> I'm having a hard time understanding where you are coming from.
> 
> *EVERY* single email client allows you to specify multiple recipients
> as a comma-separated list. Even Mercurial accepts comma-separated
> lists when to/cc are specified in the .hgrc file, or when input
> interactively into the prompt. 'git send-email' supports multiple
> addresses separated by commas. Even if you write your MIME headers by
> hand, you can use commas. This is a universal convention in email
> software.

Relax dude; This is clearly a clash of convention from different
domains. Mercurial command line options that take multiple values, don't
use commas to separate them. This is what I am arguing, not what email
programs (mercurial isn't one) do or don't. I didn't even say I was
completely opposed or anything, just that I found it a bit weird.

Convention means something to the user experience; both sets of
conventions, I am sure.

/Sune



More information about the Mercurial-devel mailing list