[PATCH 0 of 3] Add option for operating on queue repository

Dan Villiom Podlaski Christiansen danchr at gmail.com
Mon Jul 6 16:19:47 CDT 2009

On 6 Jul 2009, at 16:45, Greg Ward wrote:

> On Mon, Jul 6, 2009 at 9:46 AM, Dan Villiom Podlaski
> Christiansen<danchr at gmail.com> wrote:
>> On 06/07/2009, at 15.33, Greg Ward wrote:
>>> I still think a separate standalone 'mq' script is a more elegant  
>>> and
>>> less invasive approach. I started hacking one together on Friday,  
>>> but
>>> did not get it working and then forgot about it over the weekend.   
>>> If
>>> anyone else wants to take over, I'll attach what I've got so far.
>> While such a script is useful, I doubt it'd see much use outside  
>> the core
>> Mercurial community, unless it was installed by default. Not  
>> everyone runs
>> Mercurial from the source directory, and some users may not even  
>> have one :)
> Sorry, I should have been clearer: that is exactly what I'm proposing.
> /usr/bin/mq would be installed at the same time as /usr/bin/hg.
> (Unless some packager puts MQ into a separate package, I suppose.)

It seems to me that such a command script would lead to a fair amount  
of user confusion: How would it behave when mq is disabled? Which MQ  
operations should be handled by it, and which should be handled by the  
regular script?

Also, are you sure mq — an arguably advanced and possibly destructive  
extension — should be elevated to a visibility similar to the rest of  
Mercurial? In my opinion, that's what making it the second command  
installed would do.


Dan Villiom Podlaski Christiansen
danchr at gmail.com

More information about the Mercurial-devel mailing list