Read about our upcoming Code of Conduct on this issue

Commit 70feb1e4 authored by Marcin Kasperski's avatar Marcin Kasperski
Browse files

(doc) Some doc updates, heptapod instead of bitbucket in examples

parent 48803edd8205
......@@ -188,15 +188,16 @@ directory). For example, write there::
acme.prefix = hg.acme.com/repositories
acme.username = johnny
acme.schemes = http https
bitbucket.prefix = https://bitbucket.org
bitbucket.username = Mekk
heptapod.prefix = https://foss.heptapod.net
heptapod.username = Mekk
mydep.prefix = https://dev.acmeorg.com
mydep.username = drmartin
and as long as you use ``acme`` alias for repositories like
``https://hg.acme.com/repositories/my_beautiful_app``, username
``johnny`` will be used, and the same password reused. Similarly
any ``hg push bitbucket`` will share the same password.
any ``hg push heptapod`` will assume username ``Mekk`` and share
the same password.
With such config repository-level ``.hg/hgrc`` need only contain
``[paths]``.
......@@ -211,8 +212,8 @@ Additional advantage of this method is that it works also during
prefix as above, and::
[path_pattern]
bitbucket.local = ~/devel/{below}
bitbucket.remote = https://bitbucket.org/Mekk/{below:/=-}
heptapod.local = ~/devel/mercurial/{below}
heptapod.remote = https://foss.heptapod.net/mercurial/{below:/=-}
so all my repositories understand ``hg push bitbucket`` without
any repository-level configuration.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment