|
Size: 663
Comment: Renamed extension
|
Size: 1525
Comment: remove category
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| == subpaths == | == projrc == |
| Line 6: | Line 6: |
| ''Author: Martin Geisler'' | ''Author: MartinGeisler'' |
| Line 8: | Line 8: |
| Download site: http://bitbucket.org/mg/subpaths | Download site: http://bitbucket.org/aragost/projrc |
| Line 12: | Line 12: |
| This extension makes Mercurial parse .hg/subpaths for additional [subpaths] remappings. The file is transferred unconditionally on clone and on pull (but not on push). This is the second part of the SubrepoRemappingPlan. | This extension makes Mercurial parse ''`.hg/projrc`'' for additional configuration settings. The file is transferred unconditionally on clone and on pull (but never on push). This can be used to implement the second part of the SubrepoRemappingPlan. |
| Line 15: | Line 17: |
| Configure your .hgrc to enable the extension by adding following lines: | Configure your ''`.hgrc`'' to enable the extension by adding following lines: |
| Line 19: | Line 21: |
| subpaths = path/to/subpaths/subpaths.py | projrc = path/to/projrc/projrc.py |
| Line 22: | Line 24: |
| ---- CategoryExtension CategoryExtensionsByOthers |
=== Load Order === The settings in the ''`.hg/projrc`'' file are meant to be used as additional ''system settings'', which means that the extension tries hard to load them in this order: 1. System configuration files (''`/etc/mercurial/hgrc`'', ''`C:\mercurial\mercurial.ini`'' and friends) 2. Project specific configuration (''`.hg/projrc`'') 3. User configuration files (''`$HOME/.hgrc`'', ''`%HOME%\.hgrc`'', and ''`%HOME%\mercurial.ini`'') 4. Repository specific configuration (''`.hg/hgrc`'') This is so that users can disable extensions loaded in the ''`.hg/projrc`'' file. === Caveats === While you can enable extensions in the ''`.hg/projrc`'' file, you cannot ''disable'' extensions with it. This is because Mercurial enables the extensions loaded from the normal configuration files before `projrc` gets a chance to loads the ''`.hg/projrc`'' file. |
projrc
This extension is not distributed with Mercurial.
Author: MartinGeisler
Download site: http://bitbucket.org/aragost/projrc
Overview
This extension makes Mercurial parse .hg/projrc for additional configuration settings. The file is transferred unconditionally on clone and on pull (but never on push).
This can be used to implement the second part of the SubrepoRemappingPlan.
Configuration
Configure your .hgrc to enable the extension by adding following lines:
[extensions] projrc = path/to/projrc/projrc.py
Load Order
The settings in the .hg/projrc file are meant to be used as additional system settings, which means that the extension tries hard to load them in this order:
System configuration files (/etc/mercurial/hgrc, C:\mercurial\mercurial.ini and friends)
Project specific configuration (.hg/projrc)
User configuration files ($HOME/.hgrc, %HOME%\.hgrc, and %HOME%\mercurial.ini)
Repository specific configuration (.hg/hgrc)
This is so that users can disable extensions loaded in the .hg/projrc file.
Caveats
While you can enable extensions in the .hg/projrc file, you cannot disable extensions with it. This is because Mercurial enables the extensions loaded from the normal configuration files before projrc gets a chance to loads the .hg/projrc file.