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

mail settings
Submitter Jordi Gutiérrez Hermoso
Date Oct. 8, 2014, 9:42 p.m.
Message ID <8b24e30d30e8f9b95ef1.1412804521@Iris>
Download mbox | patch
Permalink /patch/6161/
State Accepted
Headers show


Jordi Gutiérrez Hermoso - Oct. 8, 2014, 9:42 p.m.
# HG changeset patch
# User Jordi Gutiérrez Hermoso <>
# 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


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