Making -U the default setting for mq patches created with qnew

Jeff Walden jwalden+hg at MIT.EDU
Mon Dec 15 14:34:13 CST 2008


On 15.12.08 09:20, Peter Arrenbrecht wrote:
>> We have to remind people to add the commit message and can't get around
>> that.  However, it would be great if, in the case that someone's using mq
>> and uploads directly from .hg/patches (of the three suggested methods, the
>> only one that requires help adding a username), we didn't have to remind
>> them to add a username.  (We could add [defaults] qnew = -U to the
>> recommended .hgrc [I've done so in mine to avoid this problem], but I think
>> we don't want to enable mq or include mq-specific configuration in the
>> recommended settings, or even to point to it in instructions -- better to
>> tell people individually and let them enable as they see fit.)  *Not* adding
>> a username and committing already assumes the current user's name; is there
>> a good reason mq shouldn't do the same with qnew?  I can't really think of a
>> down side to adding user information to every mq patch.
>
> Just adding [defaults] qnew=-U does not mean you have to activate mq,
> no? So you could just ship the default in case people later do enable
> mq.

I doubt we want mq-specific config options when we don't have mq enabled, as I noted in the middle of that paragraph in the parenthesized sentence.  If it's there, we have to explain what it is, which means we have to explain what mq is and why the setting is useful, and we're trying not to make things any more complicated than they need to be.

Jeff


More information about the Mercurial-devel mailing list