Mercurial > hg
comparison doc/hgrc.5.txt @ 4642:7c5428853566
Merge with crew-stable
author | Patrick Mezard <pmezard@gmail.com> |
---|---|
date | Wed, 20 Jun 2007 22:05:43 +0200 |
parents | 63b9d2deed48 54b735135fd3 |
children | cfa477946181 |
comparison
equal
deleted
inserted
replaced
4640:178778ca648f | 4642:7c5428853566 |
---|---|
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 | |
331 hooks on platforms like Windows. For instance, $HG_PARENT2 will | |
332 not be available under Windows for non-merge changesets while being | |
333 set to an empty value under Unix-like systems. | |
334 | |
330 The syntax for Python hooks is as follows: | 335 The syntax for Python hooks is as follows: |
331 | 336 |
332 hookname = python:modulename.submodule.callable | 337 hookname = python:modulename.submodule.callable |
333 | 338 |
334 Python hooks are run within the Mercurial process. Each hook is | 339 Python hooks are run within the Mercurial process. Each hook is |