Browsing Thai translation

348.

The command that will be executed.
To execute a Mercurial command use "hg" (rather than "hg.exe") as the executable command.
You can use several {VARIABLES} to compose your command.
Common variables:
- {ROOT}: The path to the current repository root.
- {REV} / {REVID}: Selected revisions numbers / hexadecimal revision id hashes respectively formatted as a revset expression.
- {SELECTEDFILES}: The list of files selected by the user on the revision details file list.
- {FILES}: The list of files touched by the selected revisions.
- {ALLFILES}: All the files tracked by Mercurial on the selected revisions.
Pair selection variables:
- {REV_A} / {REVID_A}: the first selected revision number / hexadecimal revision id hash respectively.
- {REV_B} / {REVID_B}: the second selected revision number / hexadecimal revision id hash respectively.

372.

Run before creating a tag. Exit status 0 allows the tag to be created. Non-zero status will cause the tag to fail. ID of changeset to tag is in <tt>$HG_NODE</tt>. Name of tag is in <tt>$HG_TAG</tt>. Tag is local if <tt>$HG_LOCAL=1</tt>, in repository if <tt>$HG_LOCAL=0</tt>.

373.

Run after a changegroup has been added via push, pull or unbundle, but before the transaction has been committed. Changegroup is visible to hook program. This lets you validate incoming changes before accepting them. Passed the ID of the first new changeset in <tt>$HG_NODE</tt> and last in <tt>$HG_NODE_LAST</tt>. Exit status 0 allows the transaction to commit. Non-zero status will cause the transaction to be rolled back and the push, pull or unbundle will fail. URL that was source of changes is in <tt>$HG_URL</tt>.

374.

Run after a changeset has been created but the transaction not yet committed. Changeset is visible to hook program. This lets you validate commit message and changes. Exit status 0 allows the commit to proceed. Non-zero status will cause the transaction to be rolled back. ID of changeset is in <tt>$HG_NODE</tt>. Parent changeset IDs are in <tt>$HG_PARENT1</tt> and <tt>$HG_PARENT2</tt>.

375.

Run before updating the working directory. Exit status 0 allows the update to proceed. Non-zero status will prevent the update. Changeset ID of first new parent is in <tt>$HG_PARENT1</tt>. If merge, ID of second new parent is in <tt>$HG_PARENT2</tt>.

376.

Run after listing pushkeys (like bookmarks) in the repository. The key namespace is in <tt>$HG_NAMESPACE</tt>. <tt>$HG_VALUES</tt> is a dictionary containing the keys and values.

377.

Run after a pushkey (like a bookmark) is added to the repository. The key namespace is in <tt>$HG_NAMESPACE</tt>, the key is in <tt>$HG_KEY</tt>, the old value (if any) is in <tt>$HG_OLD</tt>, and the new value is in <tt>$HG_NEW</tt>.

378.

Run after a tag is created. ID of tagged changeset is in <tt>$HG_NODE</tt>. Name of tag is in <tt>$HG_TAG</tt>. Tag is local if <tt>$HG_LOCAL=1</tt>, in repository if <tt>$HG_LOCAL=0</tt>.

379.

Run after updating the working directory. Changeset ID of first new parent is in <tt>$HG_PARENT1</tt>. If merge, ID of second new parent is in <tt>$HG_PARENT2</tt>. If the update succeeded, <tt>$HG_ERROR=0</tt>. If the update failed (e.g. because conflicts not resolved), <tt>$HG_ERROR=1</tt>.

573.

Before graft, you must <a href="commit"><b>commit</b></a>, <a href="shelve"><b>shelve</b></a> to patch, or <a href="discard"><b>discard</b></a> changes.