Mercurial > hg
changeset 4661:a7e9b6b1adeb
Backed out changeset cfa477946181824f4c769580ebf59710090ba08a
Only printenv was changed, not the actual execution of hooks.
And not setting an empty value might cause problems on platforms
which can't always remove variables from the environment.
| author | Thomas Arendsen Hein <thomas@intevation.de> |
|---|---|
| date | Thu, 21 Jun 2007 10:00:59 +0200 |
| parents | cfa477946181 |
| children | f9b8ea362b49 |
| files | doc/hgrc.5.txt |
| diffstat | 1 files changed, 4 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/hgrc.5.txt Thu Jun 21 09:45:33 2007 +0200 +++ b/doc/hgrc.5.txt Thu Jun 21 10:00:59 2007 +0200 @@ -327,9 +327,10 @@ Also, hooks like "commit" will be called in all contexts that generate a commit (eg. tag) and not just the commit command. - Note2: Environment variables with empty values will not be passed to - hooks. For instance, $HG_PARENT2 will not be set for non-merge - changesets. + Note2: Environment variables with empty values may not be passed to + hooks on platforms like Windows. For instance, $HG_PARENT2 will + not be available under Windows for non-merge changesets while being + set to an empty value under Unix-like systems. The syntax for Python hooks is as follows: