Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
mercurial-devel
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
mercurial
mercurial-devel
Commits
d5f61613
Commit
d5f61613
authored
13 years ago
by
Martin Geisler
Browse files
Options
Downloads
Patches
Plain Diff
doc: improve merge between hgrc.5 and config help topic
parent
323c11da
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/hgrc.5.txt
+0
-3
0 additions, 3 deletions
doc/hgrc.5.txt
mercurial/help/config.txt
+16
-54
16 additions, 54 deletions
mercurial/help/config.txt
with
16 additions
and
57 deletions
doc/hgrc.5.txt
+
0
−
3
View file @
d5f61613
...
...
@@ -19,9 +19,6 @@
Synopsis
--------
The Mercurial system uses a set of configuration files to control
aspects of its behavior.
.. include:: ../mercurial/help/config.txt
Author
...
...
This diff is collapsed.
Click to expand it.
mercurial/help/config.txt
+
16
−
54
View file @
d5f61613
Mercurial
reads configuration data from several files, if they exist.
Below we list the most specific file first
.
The
Mercurial
system uses a set of configuration files to control
aspects of its behavior
.
...
...
@@ -3,3 +3,5 @@
On Windows, these configuration files are read:
The configuration files use a simple ini-file format. A configuration
file consists of sections, led by a ``[section]`` header and followed
by ``name = value`` entries::
...
...
@@ -5,11 +7,5 @@
- ``<repo>\.hg\hgrc``
- ``%USERPROFILE%\.hgrc``
- ``%USERPROFILE%\mercurial.ini``
- ``%HOME%\.hgrc``
- ``%HOME%\mercurial.ini``
- ``C:\mercurial\mercurial.ini`` (unless regkey or hgrc.d\ or mercurial.ini found)
- ``HKEY_LOCAL_MACHINE\SOFTWARE\Mercurial`` (unless hgrc.d\ or mercurial.ini found)
- ``<hg.exe-dir>\hgrc.d\*.rc`` (unless mercurial.ini found)
- ``<hg.exe-dir>\mercurial.ini``
[ui]
username = Firstname Lastname <firstname.lastname@example.net>
verbose = True
...
...
@@ -15,3 +11,4 @@
On Unix, these files are read:
The above entries will be referred to as ``ui.username`` and
``ui.verbose``, respectively. See the Syntax section below.
...
...
@@ -17,8 +14,4 @@
- ``<repo>/.hg/hgrc``
- ``$HOME/.hgrc``
- ``/etc/mercurial/hgrc``
- ``/etc/mercurial/hgrc.d/*.rc``
- ``<install-root>/etc/mercurial/hgrc``
- ``<install-root>/etc/mercurial/hgrc.d/*.rc``
Files
-----
...
...
@@ -24,7 +17,8 @@
Mercurial reads configuration data from several files, if they exist.
These files do not exist by default and you will have to create the
appropriate configuration files yourself: global configuration like
the username setting is typically put into
``%USERPROFILE%\mercurial.ini`` or ``$HOME/.hgrc`` and local
configuration is put into the per-repository ``<repo>/.hg/hgrc`` file.
...
...
@@ -25,41 +19,9 @@
These files do not exist by default and you will have to create the
appropriate configuration files yourself: global configuration like
the username setting is typically put into
``%USERPROFILE%\mercurial.ini`` or ``$HOME/.hgrc`` and local
configuration is put into the per-repository ``<repo>/.hg/hgrc`` file.
If there is a per-repository configuration file which is not owned by
the active user, Mercurial will warn you that the file is skipped::
not trusting file <repo>/.hg/hgrc from untrusted user USER, group GROUP
If this bothers you, the warning can be silenced (the file would still
be ignored) or trust can be established. Use one of the following
settings, the syntax is explained below:
- ``ui.report_untrusted = False``
- ``trusted.users = USER``
- ``trusted.groups = GROUP``
The configuration files for Mercurial use a simple ini-file format. A
configuration file consists of sections, led by a ``[section]`` header
and followed by ``name = value`` entries::
[ui]
username = Firstname Lastname <firstname.lastname@example.net>
verbose = True
The above entries will be referred to as ``ui.username`` and
``ui.verbose``, respectively. Please see the hgrc man page for a full
description of the possible configuration values:
- on Unix-like systems: ``man hgrc``
- online: http://www.selenic.com/mercurial/hgrc.5.html
Files
-----
Mercurial reads configuration data from several files, if they exist.
The names of these files depend on the system on which Mercurial is
installed. ``*.rc`` files from a single directory are read in
alphabetical order, later ones overriding earlier ones. Where multiple
...
...
@@ -74,7 +36,7 @@
this file override options in all other configuration files. On
Unix, most of this file will be ignored if it doesn't belong to a
trusted user or to a trusted group. See the documentation for the
t
rusted
_
section below for more details.
T
rusted section below for more details.
| (Unix) ``$HOME/.hgrc``
| (Windows) ``%USERPROFILE%\.hgrc``
...
...
@@ -106,8 +68,8 @@
in ``/shared/tools/etc/mercurial/hgrc``. Options in these files apply
to all Mercurial commands executed by any user in any directory.
| (Windows) ``<install-dir>\Mercurial.ini``
| (Windows) ``<install-dir>\hgrc.d\*.rc``
| (Windows) ``<install-dir>\Mercurial.ini``
**or**
| (Windows) ``<install-dir>\hgrc.d\*.rc``
**or**
| (Windows) ``HKEY_LOCAL_MACHINE\SOFTWARE\Mercurial``
Per-installation/system configuration files, for the system on
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment