- MERCURIAL WINDOWS HOOK ON COMMIT ADD COMMENT INSTALL
- MERCURIAL WINDOWS HOOK ON COMMIT ADD COMMENT PATCH
- MERCURIAL WINDOWS HOOK ON COMMIT ADD COMMENT DOWNLOAD
There should be a way to show graphically the branch and merge points within the revision log view.
MERCURIAL WINDOWS HOOK ON COMMIT ADD COMMENT PATCH
Furthermore, if you declare such a Mercurial repository to be a MQ repository, then all the patches will be correctly rendered as patches, regardless of the patch name (see r6462 for details). If you have applied mq patches in your repository, Trac will show the corresponding patch names as Tags: in the changeset view.Īlso, with the 0.12 branch of the plugin (and the MultipleRepositorySupport branch of Trac), you can browse jointly the main repository and the repository for the associated Mercurial queue, if any, ie if you versioned your patch queue using hg qinit -c and hg qcommit. Since r6443, the MQ extension is supported. There is also support for visual blame annotations: In Mercurial, a branch within a repository corresponds to a head, ie a changeset without children: The TracBrowser View revision form has been extended with pulldown menus for jumping to a given tag or branch. The tag: prefix can be used to refer to symbolic tags, although this is not a requirement, because using cset:tip would work too.įinally, the branch: prefix has a special meaning, as this will not select the specified revision, but the head which is reachable from that revision. Plain changeset numbers are also recognized, provided they are long enough (12 to 40).Īlso, it is possible to refer to changesets using the changeset: prefix, or cset: or chgset:, for hgweb compatibility. The Wiki syntax has been extended a bit, to cope with the hexadecimal notation of hg changesets. In case there are additional parents or children, these are shown as additional changeset properties ( Parents or Children), placed below the Author property and above the Message property.Īnother additional changeset property is the list of Tags that might be associated with a changeset. Therefore, Previous Changeset is a link to the first parent, and Next Changeset is a link to the first child. This means a changeset can have multiple parents (0, 1 or 2) and multiple children as well (0 to n).
Instead of a flat history of successive changesets, we actually navigate a DAG of changesets. In Mercurial, the Previous Changeset/ Next Changeset navigation is not purely sequential, as it is in Subversion. Mercurial Changesets Changeset Navigation The performance is acceptable, even if there is currently no caching in the database, see #8417.įor those used to Subversion in general and Subversion repository browsing in Trac in particular, there are a few differences worth noting. Mercurial support is basic, but works well and has been tested on the Mercurial repository itself. If you installed the egg globally and you are modifying an existing Trac environment to use the Mercurial backend, then you have to explicitly enable the plugin in TracIni. For general instructions about plugins, see also TracPlugins.
MERCURIAL WINDOWS HOOK ON COMMIT ADD COMMENT INSTALL
The TracMercurial plugin egg should be added to the plugins folder of the environment, or it can be globally installed: python setup.py install or a python setup.py develop. If the repository is not already local, simply hg clone it. Thanks to the distributed nature of Mercurial, that's always possible. The configuration has to be done on the Trac side, there's nothing to do on the Mercurial repository side, except for the fact that the repository should be made accessible as a local repository. You may also want to experiment with Mercurial:HackableMercurial distribution. Note: Mercurial's library.zip contains pyd-files, which normal Python import can't use (py2exe uses a special importer that allows that), but if you unzip library.zip somewhere and add that directory, it will work on Windows (tested with tracd).Īlternatively, you can install the pre-built Mercurial Python modules from or
However, it is not possible to achieve this using PYTHONPATH and PATH: it fails with ImportError: No module named handlers due to library.zip coming in the sys.path before the standard library. On Windows, it looks like it is possible to re-use the Mercurial library coming from the installer, see this mail. We try to maintain backward compatibility with versions of Mercurial as old as 1.1, up to the latest.
MERCURIAL WINDOWS HOOK ON COMMIT ADD COMMENT DOWNLOAD
You can download Mercurial itself from Hg:Download. The latest version is available on PyPI. If you want to get a specific revision, add an svn up -rxxx step to the instructions below, after the checkout. Mercurial itself is released under the GPLv2 license.ĭownload and Installation Releases and compatibility matrix Versionīranches/1.0-stable (1.0.x), branches/1.2-stable (1.2.x), trunk (1.3.x)īranches/1.0-stable (1.0.x), trunk (1.1.x)Ĭonsult the version table to check which version you need for your version of Trac.