[PATCH 1 of 2 V3] config: give a more detailed sample repo config

Jordi Gutiérrez Hermoso jordigh at octave.org
Wed Oct 8 16:42:01 CDT 2014


# HG changeset patch
# User Jordi Gutiérrez Hermoso <jordigh at octave.org>
# Date 1412768751 14400
#      Wed Oct 08 07:45:51 2014 -0400
# Node ID 8b24e30d30e8f9b95ef1284da81746a1f3e0ee64
# Parent  a1eb21f5caea4366310e32aa85248791d5bbfa0c
config: give a more detailed sample repo config

Some examples of the typical configurations that one might want to do
in an .hg/hgrc file. This includes a default-push that happens to
point to the same location as my-fork.

I insist on the myfork terminology for a server-side clone. Bitbucket,
Github, and others have widely popularised this meaning of "fork".

This also includes a gentle nudge to use a repo-specific username,
which is something that people might not instinctively realise is an
option.

diff --git a/mercurial/ui.py b/mercurial/ui.py
--- a/mercurial/ui.py
+++ b/mercurial/ui.py
@@ -28,6 +28,18 @@ username =
 
     'local':
 """# example repository config (see "hg help config" for more info)
+[paths]
+# path aliases to other clones of this repo in URLs or filesystem paths
+# (see "hg help config.paths" for more info)
+#
+# default      = http://example.com/hg/example-repo
+# default-push = ssh://jdoe@example.net/hg/jdoes-fork
+# my-fork      = ssh://jdoe@example.net/hg/jdoes-fork
+# my-clone     = /home/jdoe/jdoes-clone
+
+[ui]
+# name and email (local to this repository, optional), e.g.
+# username = Jane Doe <jdoe at example.com>
 """,
 
     'global':


More information about the Mercurial-devel mailing list