comparison doc/hgrc.5.txt @ 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 ecea4de3104e
comparison
equal deleted inserted replaced
4660:cfa477946181 4661:a7e9b6b1adeb
325 generic pre- and post- command hooks as they are guaranteed to be 325 generic pre- and post- command hooks as they are guaranteed to be
326 called in the appropriate contexts for influencing transactions. 326 called in the appropriate contexts for influencing transactions.
327 Also, hooks like "commit" will be called in all contexts that 327 Also, hooks like "commit" will be called in all contexts that
328 generate a commit (eg. tag) and not just the commit command. 328 generate a commit (eg. tag) and not just the commit command.
329 329
330 Note2: Environment variables with empty values will not be passed to 330 Note2: Environment variables with empty values may not be passed to
331 hooks. For instance, $HG_PARENT2 will not be set for non-merge 331 hooks on platforms like Windows. For instance, $HG_PARENT2 will
332 changesets. 332 not be available under Windows for non-merge changesets while being
333 set to an empty value under Unix-like systems.
333 334
334 The syntax for Python hooks is as follows: 335 The syntax for Python hooks is as follows:
335 336
336 hookname = python:modulename.submodule.callable 337 hookname = python:modulename.submodule.callable
337 338