Doc update: advertise the possibility to include a password in the URL

[Patrick Mézard]

Andreas Hartmetz a écrit :
> Hi all,
> 
> My name is Andreas Hartmetz and I'm new here. I have been using hg for a 
> couple of months, mostly to work on KDE using the mq extension.
> I also try to push mercurial at KDE sometimes [we are not yet ready to move 
> away from svn] - lately some support seems to be building independently so 
> things are not looking too bad.
> Anyhow...
> 
> I read the help of "hg push" which doesn't mention the possibility to specify 
> a password in the URL. While this is a standard "feature" of URLs I thought 
> hg wouldn't support it - because hg's documentation is usually very 
> thorough :)
> 
> As suggested by mpm on #mercurial here is a patch to include the possibility 
> of a password in the documentation:
> 
> 
> diff -r f67d1468ac50 mercurial/commands.py
> --- a/mercurial/commands.py     Fri Jun 27 18:28:45 2008 -0500
> +++ b/mercurial/commands.py     Sat Jun 28 02:13:08 2008 +0200
> @@ -2030,9 +2030,9 @@
>      Valid URLs are of the form:
> 
>        local/filesystem/path (or file://local/filesystem/path)
> -      http://[user@]host[:port]/[path]
> -      https://[user@]host[:port]/[path]
> -      ssh://[user@]host[:port]/[path]
> +      http://[user[:pass]@]host[:port]/[path]
> +      https://[user[:pass]@]host[:port]/[path]
> +      ssh://[user[:pass]@]host[:port]/[path]
>        static-http://host[:port]/[path]
> 
>      Paths in the local filesystem can either point to Mercurial
> @@ -2092,9 +2092,9 @@
>      Valid URLs are of the form:
> 
>        local/filesystem/path (or file://local/filesystem/path)
> -      ssh://[user@]host[:port]/[path]
> -      http://[user@]host[:port]/[path]
> -      https://[user@]host[:port]/[path]
> +      ssh://[user[:pass]@]host[:port]/[path]
> +      http://[user[:pass]@]host[:port]/[path]
> +      https://[user[:pass]@]host[:port]/[path]
> 
>      An optional identifier after # indicates a particular branch, tag,
>      or changeset to push. If -r is used, the named changeset and all its

In crew as 4a8b9cf62a6b, thanks !

FYI, it's easier to integrate such a patch when not embedded in the email message. Also, the export format, or even better the patchbomb extension, add useful metadata.


--
Patrick Mézard