First draft for clone -u

Adrian Buehlmann adrian at cadifra.com
Wed Oct 21 17:16:15 CDT 2009


On 21.10.2009 23:12, Augie Fackler wrote:
> On Oct 21, 2009, at 3:43 PM, Adrian Buehlmann wrote:
> 
>> On 21.10.2009 22:11, Peter Arrenbrecht wrote:
>>> On Wed, Oct 21, 2009 at 10:02 PM, Bryan O'Sullivan <bos at serpentine.com 
>>>> wrote:
>>>> On Wed, Oct 21, 2009 at 12:37 PM, Adrian Buehlmann <adrian at cadifra.com 
>>>> wrote:
>>>>> I started trying to add option -u to the clone command.
>>>> It would be good to know what the difference is between this and - 
>>>> r. I think
>>>> I can see it, but it needs explaining anyway.
>>> I guess the text for -r needs fixing. Like:
>>>
>>> -r  clone only this revision and all its ancestors
>> A revision always implies all its ancestors by definition --
>> a fundamental concept of every DVCS.
> 
> Sure, but if you don't say this, you *will* get support requests  
> asking why it pulls in "so much stuff I don't want." Better to head it  
> off now in the help text.
> 
>> Not sure we need to repeat that in the text of this specific
>> option.
>>
>> Also the help text already has:
>>
>>    If you use the -r/--rev option to clone up to a specific  
>> revision, no
>>    subsequent revisions (including subsequent tags) will be present  
>> in the
>>    cloned repository. This option implies --pull, even on local  
>> repositories.
>>
>> But I'm fine with changing it to
>>
>> -r  clone only this revision, tag or branch
> 
> Add "and ancestors" - see above about confusing users.
> 

Ok. I suggest you fix the text for -r in a separate
patch. My patch does not touch the option text for -r.
And I do not intend to do it in this patch.


More information about the Mercurial-devel mailing list