[Python-Dev] devguide: Fix a silly statement.

[Georg Brandl]

Am 10.02.2011 19:27, schrieb Brett Cannon:
> On Wed, Feb 9, 2011 at 23:10, Georg Brandl <g.brandl at gmx.net> wrote:
>> Am 09.02.2011 23:58, schrieb brett.cannon:
>>> brett.cannon pushed 7101df1bd817 to devguide:
>>>
>>> http://hg.python.org/devguide/rev/7101df1bd817
>>> changeset:   291:7101df1bd817
>>> branch:      hg_transition
>>> tag:         tip
>>> user:        Brett Cannon <brett at python.org>
>>> date:        Wed Feb 09 14:58:17 2011 -0800
>>> summary:
>>>   Fix a silly statement.
>>>
>>> files:
>>>   setup.rst
>>>
>>> diff --git a/setup.rst b/setup.rst
>>> --- a/setup.rst
>>> +++ b/setup.rst
>>> @@ -34,8 +34,7 @@
>>>  :abbr:`VCS`. It also means you will have better tool
>>>  support through the VCS as it will provide a diff tool, etc.
>>>
>>> -To get a read-only checkout of CPython's source, you need a working copy the
>>> -source code. To get a read-only checkout of
>>> +To get a read-only checkout of
>>>  the :ref:`in-development <indevbranch>` branch of Python, run::
>>>
>>>      hg clone http://hg.python.org/cpython
>>
>> This statement is still somewhat silly, as a) you get a clone, not a checkout
>> and b) it is not read only in any way: you can commit just fine.  The only
>> difference will be the entry in .hg/hgrc pointing the default repo to something
>> you can't push to.
>>
>> Skimming through, the whole section "Checking out the code" is still way too
>> SVN-point of viewy (e.g. you always get all branches anyway).
> 
> I'll take another pass, but do realize this needs to be something that
> can easily be understood by someone who has never used hg before, so I
> can't get too technically accurate while ignoring a possible base
> ignorance of hg and DVCSs as a whole.

Well, it's no good to keep using CVCS terms and mislead users.  That the
"checkout" is not a checkout but a full repository is about the most important
fact about a hg (or any DVCS) clone.

Georg