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

login
register
mail settings
Submitter Jordi Gutiérrez Hermoso
Date Oct. 6, 2014, 8:41 p.m.
Message ID <eaf28cae9dedb26c7a78.1412628089@Iris>
Download mbox | patch
Permalink /patch/6148/
State Superseded
Commit 5a831e4e6d7a4a33651f51c73ff413cb3d77eb9e
Headers show

Comments

Jordi Gutiérrez Hermoso - Oct. 6, 2014, 8:41 p.m.
# HG changeset patch
# User Jordi Gutiérrez Hermoso <jordigh@octave.org>
# Date 1412353066 14400
#      Fri Oct 03 12:17:46 2014 -0400
# Node ID eaf28cae9dedb26c7a78a371b7435589a1482cf3
# Parent  889789a2ca9f19755bf0d302c8671f850e42a059
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.

Patch

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@example.com>
 """,
 
     'global':