#Mercurial windows hook on local commit add comment manual
Or other, or internal:dump to leave files in the workingĭirectory for manual merging. Chose internal:merge to forceĬonflict markers, internal:prompt to always select local On your system or use its internal merge tool that leaves conflict Unspecified, Mercurial will use the first applicable tool it finds TortoiseHg ¶ UI Language: Specify your preferred user interface language (restart needed) 3-way Merge Tool: Graphical merge program for resolving merge conflicts. The user and repository configuration files may not exist until you runĦ.1.1.
Override many configurables per-repository (a common example is toĬonfigure a username for use in a specific repository). (remote repository aliases) and web settings, though it is possible to Global user settings, and only use the repository hgrc to store paths Most TortoiseHg users will want to store all configurables in their The dialog, or directly edit the file in your configured visual editor. You may toggle between the two modes using the combo box at the top of Suggestion by only operating in two modes: Global edits your user Mercurial.ini file Repository edits a repository. The TortoiseHg Settings dialog enforces this Instead, you should makeĬhanges to your user Mercurial.ini and/or the repository That you do not make changes to this file. The site-wide file can be overwritten on upgrades so it is recommended A per-repository configuration file in repo-root\.hg\hgrc Thisįile is read last and can override site-wide and user global settings.This file is read second and thus can override settings in the This file is read first and thus has the lowest priority.Ĭ:\Documents and Settings\username\Mercurial.ini
Mercurial on Windows has a three-tier configuration system.Ĭ:\Program Files\TortoiseHg\Mercurial.ini
Since TortoiseHg uses Mercurial’s underlyingĬonfiguration system to store and retrieve its settings, these are The Settings dialog is used to configure both TortoiseHg and the
0 kommentar(er)
