comparison doc/hgrc.5.txt @ 4660:cfa477946181

Adjust note about variables not being set for empty values.
author Thomas Arendsen Hein <thomas@intevation.de>
date Thu, 21 Jun 2007 09:45:33 +0200
parents 7c5428853566
children a7e9b6b1adeb
comparison
equal deleted inserted replaced
4659:7a7d4937272b 4660:cfa477946181
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 may not be passed to 330 Note2: Environment variables with empty values will not be passed to
331 hooks on platforms like Windows. For instance, $HG_PARENT2 will 331 hooks. For instance, $HG_PARENT2 will not be set for non-merge
332 not be available under Windows for non-merge changesets while being 332 changesets.
333 set to an empty value under Unix-like systems.
334 333
335 The syntax for Python hooks is as follows: 334 The syntax for Python hooks is as follows:
336 335
337 hookname = python:modulename.submodule.callable 336 hookname = python:modulename.submodule.callable
338 337