First draft for clone -u
Augie Fackler
lists at durin42.com
Wed Oct 21 16:12:23 CDT 2009
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.
>
> But maybe this could be changed in a separate patch?
>
> After all, my patch does not change -r ...
>
>> And the help text needs to mention -u when it talks about -U and
>> defaulting to default, of course.
>
> Can you provide an updated help text? Or a patch for it?
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
More information about the Mercurial-devel
mailing list