[PATCH] Make the --authors option to hgext/convert expand ~

Steve Borho steve at borho.org
Wed Mar 3 16:00:05 CST 2010


On Wed, Mar 3, 2010 at 3:42 PM, Sune Foldager <cryo at cyanite.org> wrote:
> On 03-03-2010 20:07, Benoit Boissinot wrote:
>> On Wed, Mar 3, 2010 at 7:54 PM, Brendan Cully <brendan at kublai.com> wrote:
>>> On Wednesday, 03 March 2010 at 13:31, Greg Ward wrote:
>>>> IMHO no.  Because then Windows people will expect "hg clone ~/foo" or
>>>> "hg pull ~/foo" to do something meaningful.  And I don't think we
>>>> should do that.  Let Unix shells do what they do, i.e. expand wildcard
>>>> patterns before exec()'ing the child.  Windows users who want Unix
>>>> behaviour can, ummm, I dunno... use cygwin?  ;-)
>>>
>>> I don't think it's consistent for ~ to work in config files but not on
>>> the command line (IOW, hg pull ~/foo ought to work regardless of your
>>> platform). Of course, it works on both for unix because we happen to
>>> have a helpful shell. For windows, I think it makes sense to expand
>>> the path.
>>
>> I remember the same conversation, a couple years ago, but with '*'
>> instead of '~'. Can't we do the same thing and teach glob about '~' ?
>
> I agree, we should do that. We really want * to work on Windows (which
> it does), and ~ should as well, for consistency.

These are two different things, though.  The * globs generate matchers
for walking the working copy while ~ usually references files outside
of your repository.  It would be two entirely different mechanisms.

--
Steve Borho


More information about the Mercurial-devel mailing list