crew-stable/raw-rev/4d3a60d5c490, improve help text for clone -U

[Adrian Buehlmann]

http://hg.intevation.org/mercurial/crew-stable/raw-rev/4d3a60d5c490
> # HG changeset patch
> # User Dirkjan Ochtman <dirkjan at ochtman.nl>
> # Date 1211543963 -7200
> # Node ID 4d3a60d5c490b757b22df54e5591cd5530b1d44e
> # Parent 1916e629a29d7047800da70258363bafd4725081
> improve help text for clone -U
> 
> --- a/mercurial/commands.py	Thu May 22 15:48:44 2008 -0500
> +++ b/mercurial/commands.py	Fri May 23 13:59:23 2008 +0200
> @@ -519,6 +519,9 @@
>      If you use the -r option to clone up to a specific revision, no
>      subsequent revisions will be present in the cloned repository.
>      This option implies --pull, even on local repositories.
> +
> +    If the -U option is used, the new clone will contain only a repository
> +    (.hg) and no working copy (the working copy parent is the null revision).

I think

  "the new clone will only contain the store (.hg) and no working copy"

would be more accurate. See [1]

>  
>      See pull for valid source format details.
>  
> @@ -2955,7 +2958,8 @@
>           _('hg cat [OPTION]... FILE...')),
>      "^clone":
>          (clone,
> -         [('U', 'noupdate', None, _('do not update the new working directory')),
> +         [('U', 'noupdate', None,
> +          _('the clone will only contain a repository (no working copy)')),
>            ('r', 'rev', [],
>             _('a changeset you would like to have after cloning')),
>            ('', 'pull', None, _('use pull protocol to copy metadata')),

[1]
http://www.selenic.com/mercurial/wiki/index.cgi/UnderstandingMercurial:
"Mercurial repositories contain a working directory coupled with a store"