Mercurial > hg
comparison doc/hgrc.5.txt @ 4641:54b735135fd3
Document empty environment variables not being passed to hooks under Windows.
author | Patrick Mezard <pmezard@gmail.com> |
---|---|
date | Wed, 20 Jun 2007 21:35:41 +0200 |
parents | a8a8ecf909db |
children | 7c5428853566 |
comparison
equal
deleted
inserted
replaced
4639:c7371aa0c153 | 4641:54b735135fd3 |
---|---|
306 | 306 |
307 Note: In earlier releases, the names of hook environment variables | 307 Note: In earlier releases, the names of hook environment variables |
308 did not have a "HG_" prefix. The old unprefixed names are no longer | 308 did not have a "HG_" prefix. The old unprefixed names are no longer |
309 provided in the environment. | 309 provided in the environment. |
310 | 310 |
311 Note2: Environment variables with empty values may not be passed to | |
312 hooks on platforms like Windows. For instance, $HG_PARENT2 will | |
313 not be available under Windows for non-merge changesets while being | |
314 set to an empty value under Unix-like systems. | |
315 | |
311 The syntax for Python hooks is as follows: | 316 The syntax for Python hooks is as follows: |
312 | 317 |
313 hookname = python:modulename.submodule.callable | 318 hookname = python:modulename.submodule.callable |
314 | 319 |
315 Python hooks are run within the Mercurial process. Each hook is | 320 Python hooks are run within the Mercurial process. Each hook is |