<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="X-UA-Compatible" content="IE=Edge" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>8. Extensions — TortoiseHg 4.7.0 documentation</title>
<link rel="stylesheet" href="_static/tortoisehg.css" type="text/css" />
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
<script type="text/javascript" id="documentation_options" data-url_root="./" src="_static/documentation_options.js"></script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/underscore.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<script type="text/javascript" src="_static/language_data.js"></script>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="9. Use with other VCS systems" href="nonhg.html" />
<link rel="prev" title="7. Patches" href="patches.html" />
<link rel="stylesheet" href="_static/custom.css" type="text/css" />
<meta name="viewport" content="width=device-width, initial-scale=0.9, maximum-scale=0.9" />
</head><body>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<div class="section" id="module-extensions">
<span id="extensions"></span><h1>8. Extensions<a class="headerlink" href="#module-extensions" title="Permalink to this headline">¶</a></h1>
<p>This chapter describes Mercurial extensions that are shipped with
TortoiseHg binary packages for Windows. These external extensions are
included as a convenience to users, so they can be easily enabled as
soon as they are needed.</p>
<div class="section" id="hgfold">
<h2>8.1. Hgfold<a class="headerlink" href="#hgfold" title="Permalink to this headline">¶</a></h2>
<p><a class="reference external" href="https://www.mercurial-scm.org/wiki/CaseFoldExtension">hgfold</a> is a
Mercurial extension that helps Windows users deal with filename case
collisions on VFAT and NTFS.</p>
<p>It adds options to the following Mercurial commands. Type
<strong class="command">hg help <command></strong> for more information:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">up</span> <span class="o">-</span> <span class="n">allows</span> <span class="n">you</span> <span class="n">to</span> <span class="n">update</span> <span class="n">to</span> <span class="n">a</span> <span class="n">revision</span> <span class="k">with</span> <span class="n">filename</span> <span class="n">collisions</span>
<span class="n">merge</span> <span class="o">-</span> <span class="n">allows</span> <span class="n">you</span> <span class="n">to</span> <span class="n">merge</span> <span class="k">with</span> <span class="n">a</span> <span class="n">changeset</span> <span class="n">that</span> <span class="n">would</span> <span class="n">create</span> <span class="n">filename</span> <span class="n">collisions</span>
</pre></div>
</div>
<p>The extension does not currently do anything to prevent filename
collisions. See discussion on the Mercurial Wiki</p>
<p><strong>Installation</strong></p>
<p>To test the use of this plugin, you can specify it on the Mercurial
command line like this:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">hg</span> <span class="o">--</span><span class="n">config</span> <span class="s2">"extensions.fold="</span> <span class="n">status</span>
</pre></div>
</div>
<p>You may want to add it to your Mercurial.ini or a repository’s hgrc like this:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">[</span><span class="n">extensions</span><span class="p">]</span>
<span class="n">fold</span><span class="o">=</span>
</pre></div>
</div>
<p>If you do this, you can omit the –config command-line option.</p>
<p><strong>Warnings</strong></p>
<p>Like all merge operations, fold.py has to change the parents of the
working directory. It is still in early testing, so use with caution.</p>
<p>If you get an error about an unknown changeset after running
<strong class="command">hg recover</strong> try
<strong class="command">hg debugsetparents <number of tip revision></strong>.
You can find the number of the tip revision by running <strong class="command">hg log -l 2</strong>.</p>
</div>
<div class="section" id="perfarce">
<h2>8.2. Perfarce<a class="headerlink" href="#perfarce" title="Permalink to this headline">¶</a></h2>
<p><a class="reference external" href="http://www.kingswood-consulting.co.uk/hg/perfarce/">Perfarce</a> home
page.</p>
<p>This extension is documented in <a class="reference internal" href="nonhg.html#perfarce-perforce"><span class="std std-ref">Perfarce (Perforce)</span></a> section of
<a class="reference internal" href="nonhg.html"><span class="doc">Use with other VCS systems</span></a> chapter.</p>
</div>
<div class="section" id="mercurial-keyring">
<h2>8.3. Mercurial-Keyring<a class="headerlink" href="#mercurial-keyring" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li><a class="reference external" href="https://pypi.python.org/pypi/mercurial_keyring">Mercurial Keyring</a> home page</li>
<li><a class="reference external" href="https://www.mercurial-scm.org/wiki/KeyringExtension">Keyring Extension</a> wiki page</li>
</ul>
<p>Keyring extension uses services of the keyring library to securely save
authentication passwords (HTTP/HTTPS and SMTP) using system specific
password database (Gnome Keyring, KDE KWallet, OSXKeyChain, dedicated
solutions for Win32 and command line).</p>
<p><strong>What it does</strong></p>
<p>The extension prompts for the HTTP password on the first pull/push
to/from given remote repository (just like it is done by default), but
saves the password (keyed by the combination of username and remote
repository url) in the password database. On the next run it checks for
the username in <code class="file docutils literal notranslate"><span class="pre">.hg/hgrc</span></code>, then for suitable password in the password
database, and uses those credentials if found.</p>
<p>Similarly, while sending emails via SMTP server which requires
authorization, it prompts for the password on first use of given server,
then saves it in the password database and reuses on successive runs.</p>
<p>In case password turns out incorrect (either because it was invalid, or
because it was changed on the server) it just prompts the user again.</p>
<p><strong>Installation</strong></p>
<p>First, the extension must be enabled in your Mercurial.ini file as:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">[</span><span class="n">extensions</span><span class="p">]</span>
<span class="n">mercurial_keyring</span><span class="o">=</span>
</pre></div>
</div>
<p><strong>Password backend configuration</strong></p>
<p>The most appropriate password backend should usually be picked automatically,
without configuration. Still, if necessary, it can be configured using
<code class="file docutils literal notranslate"><span class="pre">~/keyringrc.cfg</span></code> file (<code class="file docutils literal notranslate"><span class="pre">keyringrc.cfg</span></code> in the home directory of
the current user).
Refer to <a class="reference external" href="https://pypi.python.org/pypi/keyring">keyring docs</a>
for more details.</p>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">On Windows XP and above, your encrypted passwords are stored in the
credentials subsystem using
<a class="reference external" href="https://msdn.microsoft.com/en-us/library/aa374804%28VS.85%29.aspx">CredRead</a> and <a class="reference external" href="https://msdn.microsoft.com/en-us/library/aa375187%28VS.85%29.aspx">CredWrite</a></p>
</div>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">On Windows 2K, the encrypted passwords are stored in the system
registry under HKCU\Software\Mercurial\Keyring.</p>
</div>
<p><strong>Repository configuration (HTTP)</strong></p>
<p>Edit repository-local <code class="file docutils literal notranslate"><span class="pre">.hg/hgrc</span></code> and save there the remote repository
path and the username, but do not save the password. For example:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">[</span><span class="n">paths</span><span class="p">]</span>
<span class="n">myremote</span> <span class="o">=</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">my</span><span class="o">.</span><span class="n">server</span><span class="o">.</span><span class="n">com</span><span class="o">/</span><span class="n">hgrepo</span><span class="o">/</span><span class="n">someproject</span>
<span class="p">[</span><span class="n">auth</span><span class="p">]</span>
<span class="n">myremote</span><span class="o">.</span><span class="n">schemes</span> <span class="o">=</span> <span class="n">http</span> <span class="n">https</span>
<span class="n">myremote</span><span class="o">.</span><span class="n">prefix</span> <span class="o">=</span> <span class="n">my</span><span class="o">.</span><span class="n">server</span><span class="o">.</span><span class="n">com</span><span class="o">/</span><span class="n">hgrepo</span>
<span class="n">myremote</span><span class="o">.</span><span class="n">username</span> <span class="o">=</span> <span class="n">mekk</span>
</pre></div>
</div>
<p>Simpler form with url-embedded name can also be used:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">[</span><span class="n">paths</span><span class="p">]</span>
<span class="n">bitbucket</span> <span class="o">=</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">User</span><span class="nd">@bitbucket</span><span class="o">.</span><span class="n">org</span><span class="o">/</span><span class="n">User</span><span class="o">/</span><span class="n">project_name</span><span class="o">/</span>
</pre></div>
</div>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">If both username and password are given in <code class="file docutils literal notranslate"><span class="pre">.hg/hgrc</span></code>, extension
will use them without using the password database. If username is not
given, extension will prompt for credentials every time, also
without saving the password. So, in both cases, it is effectively
reverting to the default behaviour.</p>
</div>
<p>Consult <a class="reference external" href="https://www.mercurial-scm.org/doc/hgrc.5.html#auth">[auth]</a>
section documentation for more details.</p>
<p><strong>Repository configuration (SMTP)</strong></p>
<p>Edit either repository-local <code class="file docutils literal notranslate"><span class="pre">.hg/hgrc</span></code>, or <code class="file docutils literal notranslate"><span class="pre">~/.hgrc</span></code> (the latter
is usually preferable) and set there all standard email and smtp properties,
including smtp username, but without smtp password. For example:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">[</span><span class="n">email</span><span class="p">]</span>
<span class="n">method</span> <span class="o">=</span> <span class="n">smtp</span>
<span class="kn">from</span> <span class="o">=</span> <span class="n">Joe</span> <span class="n">Doe</span> <span class="o"><</span><span class="n">Joe</span><span class="o">.</span><span class="n">Doe</span><span class="nd">@remote</span><span class="o">.</span><span class="n">com</span><span class="o">></span>
<span class="p">[</span><span class="n">smtp</span><span class="p">]</span>
<span class="n">host</span> <span class="o">=</span> <span class="n">smtp</span><span class="o">.</span><span class="n">gmail</span><span class="o">.</span><span class="n">com</span>
<span class="n">port</span> <span class="o">=</span> <span class="mi">587</span>
<span class="n">username</span> <span class="o">=</span> <span class="n">JoeDoe</span><span class="nd">@gmail</span><span class="o">.</span><span class="n">com</span>
<span class="n">tls</span> <span class="o">=</span> <span class="n">true</span>
</pre></div>
</div>
<p>Just as in case of HTTP, you must set username, but must not set password here
to use the extension, in other cases it will revert to the default behaviour.</p>
<p><strong>Usage</strong></p>
<p>Configure the repository as above, then just pull and push (or email) You
should be asked for the password only once (per every username +
remote_repository_url combination).</p>
</div>
<div class="section" id="projrc">
<h2>8.4. projrc<a class="headerlink" href="#projrc" title="Permalink to this headline">¶</a></h2>
<p><a class="reference external" href="https://www.mercurial-scm.org/wiki/ProjrcExtension">projrc</a> is an extension
that makes Mercurial look for and parse .hg/projrc for additional
configuration settings.The file is transferred on clone and on pull
(but never on push), after confirmation by the user, from a list of servers
that ‘’‘must’‘’ be configured by the user. For security reasons the user
‘’‘must’‘’ also select which ‘’<cite>projrc</cite>’’ configuration settings will be
transferred (i.e. no settings are transferred from any servers by default).
The user can also configure the extension to automatically accept all changes
to the .hg/projrc file.</p>
<p>This is useful for centralized setups where you want to distribute
configuration settings to all repositories with a minimum amount of setup.
In particular, it can be used to remap subrepository sources, as explained
on Mercurial’s
<a class="reference external" href="https://www.mercurial-scm.org/wiki/SubrepoRemappingPlan">SubrepoRemappingPlan</a>.</p>
<p><strong>Configuration</strong></p>
<p>This extension (as most other extensions) is disabled by default. To use
and configure you must first enable it on the Settings/Extensions panel.</p>
<p>When the extension is enabled you will see a new entry, “Projrc” on the
settings dialog. This let’s you configure the extension by setting the
following settings:</p>
<blockquote>
<div><blockquote>
<div><span class="guilabel">Request confirmation</span>
If True (the default) you’ll get a prompt whenever
the extension detects changes to the remote server’s
.hg/projrc file.
If false, the extension will automatically accept any change to the
remote .hg/projrc file.</div></blockquote>
<dl class="docutils">
<dt><span class="guilabel">Servers</span></dt>
<dd>This setting is a comma separated list of glob patterns matching
the server names of the servers that the projrc file will be pulled from.
Unless this setting is set, no .hg/projrc files will be ever
transferred from any servers.</dd>
<dt><span class="guilabel">Include</span></dt>
<dd><p class="first">This key lets you control which sections and which keys will be accepted
from the remote projrc files. This is a a comma separated list of glob
patterns that match the section or key names that will be included.
Keys names must be specified with their section name followed by a ‘.’
followed by the key name (e.g. “’‘<cite>diff.git</cite>’‘”).</p>
<p class="last">To allow all sections and all keys you can set this setting to “*”
(without the quotes).</p>
</dd>
<dt><span class="guilabel">Exclude</span></dt>
<dd><p class="first">This setting is similar to the “’‘<cite>Include</cite>’‘” setting but it has the
opposite effect. It sets an “exclude list” of settings that will not
be transferred from the common projrc files.</p>
<p class="last">The exclude list has the same syntax as the include list. If an exclusion
list is set but the inclusion list is empty or not set all non excluded
keys will be included.</p>
</dd>
<dt><span class="guilabel">Update on incoming</span></dt>
<dd><p class="first">Control whether the .hg/projrc file will be updated on incoming.
It can have the following values:</p>
<ul class="simple">
<li>never: The default. Show whether the remote projrc file has changed,
but do not update (nor ask to update) the local projrc file.</li>
<li>prompt: Look for changes to the projrc file.
If there are changes _always_ show a confirmation prompt,
asking the user if it wants to update its local projrc file.</li>
<li>auto: Look for changes to the projrc file.
Use the value of the “’‘<cite>projrc.confirm</cite>’‘” configuration key to
determine whether to show a confirmation dialog or not
before updating the local projrc file.</li>
</ul>
<p class="last">If False (the default) you’ll get a prompt whenever
the extension detects changes to the remote server’s
.hg/projrc file.
If false, the extension will automatically accept any change to the
remote .hg/projrc file.</p>
</dd>
</dl>
</div></blockquote>
<p>If both an include and an exclude lists are set, and a key matches both
the include and the exclude list, priority is given to the most explicit
key match, in the following order:</p>
<blockquote>
<div><ul class="simple">
<li>full key, exact matches are considered the most explicit (e.g.
“’‘<cite>ui.merge</cite>’‘”);</li>
<li>pattern (glob) matches are considered next (e.g.
“’‘<cite>auth.bitbucket.com.*</cite>’‘”), with the longest matching pattern being the
most explicit;</li>
<li>section level matches (e.g. “’‘<cite>ui</cite>’‘”);</li>
<li>global (“’‘<cite>*</cite>’‘”) matches.</li>
</ul>
</div></blockquote>
<p>If a key matches both an include and an exclude (glob) pattern of the same
length, the key is ‘’included’’ (i.e. inclusion takes precedence over
exclusion).</p>
<p><strong>Usage</strong></p>
<p>Once enabled and properly configured, the extension will look for
.hg/projrc files whenever you clone or pull from one of the repositories
specified on its “servers” configuration key.</p>
<p>Whenever the extension detects changes to the remote projrc file (e.g. when
you do not have a .hg/projrc file yet, or when the contents of said file
have changed on the server), you’ll receive a warning unless you have set the
“Require confirmation” setting to False (in which case the extension assumes
that you accept the changes). If you accept the changes your local .hg/projrc
file will be updated, and its settings will be taken into account by mercurial
and TortoiseHg.</p>
<p>If a local repository has a .hg/projrc file, you’ll see an extra panel
on the setting dialog. The title of the extra panel is “project settings
(.hg/projrc)”.</p>
<p>The “project settings” panel is a read-only panel that shows the settings that
are set on the local .hg/projrc file. Although you can update your local
version of the .hg/projrc file, the panel is read only to indicate that
you cannot change the remote repository’s settings, and that if the remote
repository settings change your local copy will be updated on the next pull
(if you allow it).</p>
<p>The “project settings” settings panel is shown between the “global settings” panel
and the “repository settings” panel, indicating that its settings are applied
_after_ the global settings but _before_ the local repository settings (i.e
the settings specified in the repository .hg/hgrc file).</p>
<p><strong>Additional Information</strong></p>
<p>For the most up to date information regarding this extension, to see several
detailed usage examples and to learn how to use it and configure it from the
command line, please go to the extension’s
<a class="reference external" href="https://www.mercurial-scm.org/wiki/ProjrcExtension">Wiki</a>.</p>
</div>
<div class="section" id="pbranch">
<h2>8.5. pbranch<a class="headerlink" href="#pbranch" title="Permalink to this headline">¶</a></h2>
<p>Patch Branches (<a class="reference external" href="https://www.mercurial-scm.org/wiki/PatchBranchExtension">pbranch</a>)
is a way to develop a series of patches for submission into a main
repo. It is based on topic branches, one per patch, and is thus highly
suitable for collaborative and/or long-term patch development and
maintenance.</p>
<p><a class="reference external" href="http://arrenbrecht.ch/mercurial/pbranch/">A detailed manual</a> can be found online.</p>
<p>It adds a number of commands which can be listed with
<strong class="command">hg help pbranch</strong>:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">pbackout</span> <span class="o">-</span> <span class="n">backs</span> <span class="n">out</span> <span class="n">the</span> <span class="n">current</span> <span class="n">patch</span> <span class="n">branch</span> <span class="p">(</span><span class="n">undoes</span> <span class="nb">all</span> <span class="n">its</span> <span class="n">changes</span><span class="p">)</span>
<span class="n">pdiff</span> <span class="o">-</span> <span class="n">prints</span> <span class="n">the</span> <span class="n">final</span> <span class="n">diff</span> <span class="k">for</span> <span class="n">the</span> <span class="n">current</span> <span class="ow">or</span> <span class="n">given</span> <span class="n">patch</span> <span class="n">branch</span>
<span class="n">peditmessage</span> <span class="o">-</span> <span class="n">edit</span> <span class="n">the</span> <span class="n">patch</span> <span class="n">message</span>
<span class="n">pemail</span> <span class="o">-</span> <span class="n">send</span> <span class="n">patches</span> <span class="n">by</span> <span class="n">email</span>
<span class="n">pexport</span> <span class="o">-</span> <span class="n">exports</span> <span class="n">patches</span>
<span class="n">pextdiff</span> <span class="o">-</span> <span class="n">combines</span> <span class="n">pdiff</span> <span class="ow">and</span> <span class="n">extdiff</span>
<span class="n">pgraph</span> <span class="o">-</span> <span class="nb">print</span> <span class="n">an</span> <span class="n">ASCII</span> <span class="n">art</span> <span class="n">rendering</span> <span class="n">of</span> <span class="n">the</span> <span class="n">patch</span> <span class="n">dependency</span> <span class="n">graph</span>
<span class="n">pmerge</span> <span class="o">-</span> <span class="n">merge</span> <span class="n">pending</span> <span class="n">heads</span> <span class="kn">from</span> <span class="nn">dependencies</span> <span class="n">into</span> <span class="n">patch</span> <span class="n">branches</span>
<span class="n">pmessage</span> <span class="o">-</span> <span class="nb">print</span> <span class="n">the</span> <span class="n">patch</span> <span class="n">message</span><span class="p">(</span><span class="n">s</span><span class="p">)</span>
<span class="n">pnew</span> <span class="o">-</span> <span class="n">start</span> <span class="n">a</span> <span class="n">new</span> <span class="n">patch</span> <span class="n">branch</span>
<span class="n">pstatus</span> <span class="o">-</span> <span class="nb">print</span> <span class="n">status</span> <span class="n">of</span> <span class="n">current</span> <span class="p">(</span><span class="ow">or</span> <span class="n">given</span><span class="p">)</span> <span class="n">patch</span> <span class="n">branch</span>
<span class="n">reapply</span> <span class="o">-</span> <span class="n">reverts</span> <span class="n">the</span> <span class="n">working</span> <span class="n">copy</span> <span class="n">of</span> <span class="nb">all</span> <span class="n">files</span> <span class="n">touched</span> <span class="n">by</span> <span class="n">REV</span> <span class="n">to</span> <span class="n">REV</span>
</pre></div>
</div>
<p>TortoiseHg will provide a new task tab that shows the patch dependency graph.</p>
<blockquote>
<div><div class="figure" id="id6">
<img alt="Pbranch task tab" src="_images/pbranch.png" />
<p class="caption"><span class="caption-text">Pbranch task tab</span></p>
</div>
</div></blockquote>
<p><strong>Installation</strong></p>
<p>As this extension is not installed with TortoiseHg, you have to download
it from <a class="reference external" href="https://bitbucket.org/parren/hg-pbranch">https://bitbucket.org/parren/hg-pbranch</a>. Be sure to dowload the
right one according to the Mercurial version included with TortoiseHg (see the
wiki page on the download site).
To test the use of this plugin, you can specify it on the Mercurial
command line like this:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">hg</span> <span class="o">--</span><span class="n">config</span> <span class="s2">"extensions.pbranch=C:\path</span><span class="se">\t</span><span class="s2">o\pbranch.py"</span> <span class="n">pstatus</span>
</pre></div>
</div>
<p>You may want to add it to your Mercurial.ini or a repository’s hgrc like this:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">[</span><span class="n">extensions</span><span class="p">]</span>
<span class="n">pbranch</span> <span class="o">=</span> <span class="n">C</span><span class="p">:</span>\<span class="n">path</span>\<span class="n">to</span>\<span class="n">pbranch</span><span class="o">.</span><span class="n">py</span>
</pre></div>
</div>
<p>If you do this, you can omit the –config command-line option.</p>
</div>
</div>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="main navigation">
<div class="sphinxsidebarwrapper">
<p class="logo"><a href="index.html">
<img class="logo" src="_static/thg_logo_92x50.png" alt="Logo"/>
</a></p>
<h1 class="logo"><a href="index.html">TortoiseHg</a></h1>
<h3>Navigation</h3>
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="preface.html">1. Preface</a></li>
<li class="toctree-l1"><a class="reference internal" href="intro.html">2. Introduction</a></li>
<li class="toctree-l1"><a class="reference internal" href="whatsnew.html">3. What’s New</a></li>
<li class="toctree-l1"><a class="reference internal" href="quick.html">4. A Quick Start Guide to TortoiseHg</a></li>
<li class="toctree-l1"><a class="reference internal" href="daily.html">5. TortoiseHg in daily use</a></li>
<li class="toctree-l1"><a class="reference internal" href="settings.html">6. Settings</a></li>
<li class="toctree-l1"><a class="reference internal" href="patches.html">7. Patches</a></li>
<li class="toctree-l1 current"><a class="current reference internal" href="#">8. Extensions</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#hgfold">8.1. Hgfold</a></li>
<li class="toctree-l2"><a class="reference internal" href="#perfarce">8.2. Perfarce</a></li>
<li class="toctree-l2"><a class="reference internal" href="#mercurial-keyring">8.3. Mercurial-Keyring</a></li>
<li class="toctree-l2"><a class="reference internal" href="#projrc">8.4. projrc</a></li>
<li class="toctree-l2"><a class="reference internal" href="#pbranch">8.5. pbranch</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="nonhg.html">9. Use with other VCS systems</a></li>
<li class="toctree-l1"><a class="reference internal" href="faq.html">10. Frequently Asked Questions</a></li>
<li class="toctree-l1"><a class="reference internal" href="debugging.html">11. Debugging</a></li>
</ul>
<div class="relations">
<h3>Related Topics</h3>
<ul>
<li><a href="index.html">Documentation overview</a><ul>
<li>Previous: <a href="patches.html" title="previous chapter">7. Patches</a></li>
<li>Next: <a href="nonhg.html" title="next chapter">9. Use with other VCS systems</a></li>
</ul></li>
</ul>
</div>
<div id="searchbox" style="display: none" role="search">
<h3>Quick search</h3>
<div class="searchformwrapper">
<form class="search" action="search.html" method="get">
<input type="text" name="q" />
<input type="submit" value="Go" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="footer">
©2010-2019, Steve Borho and others.
|
Powered by <a href="http://sphinx-doc.org/">Sphinx 1.8.4</a>
& <a href="https://github.com/bitprophet/alabaster">Alabaster 0.7.12</a>
|
<a href="_sources/extensions.txt"
rel="nofollow">Page source</a>
</div>
</body>
</html>
distrib
>
Mageia
>
7
>
armv7hl
>
media
>
core-updates
>
by-pkgid
>
67810d03ada515381702f7b70888f800
>
files
>
501
