diff options
| author |  Junio C Hamano <junkio@cox.net> | 2005-12-19 16:35:48 -0800 |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2005-12-19 16:38:16 -0800 |
| commit | 3aadad1b32db3555bc19dac0892d41628a8e736d (patch) | |
| tree | 9f102d3e62180816103e1cfee91071ffb81edcc6 /Documentation/howto | |
| parent | rev-list --objects: fix object list without commit. (diff) | |
| download | tgif-3aadad1b32db3555bc19dac0892d41628a8e736d.tar.xz | |
Documentation: stdout of update-hook is connected to /dev/null
Mention that update-hook does not emit its stdout to the sender.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/howto')
| -rw-r--r-- | Documentation/howto/rebuild-from-update-hook.txt | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/Documentation/howto/rebuild-from-update-hook.txt b/Documentation/howto/rebuild-from-update-hook.txt index ebd025db85..02621b54a0 100644 --- a/Documentation/howto/rebuild-from-update-hook.txt +++ b/Documentation/howto/rebuild-from-update-hook.txt @@ -10,7 +10,7 @@ The pages under http://www.kernel.org/pub/software/scm/git/docs/ are built from Documentation/ directory of the git.git project and needed to be kept up-to-date. The www.kernel.org/ servers are mirrored and I was told that the origin of the mirror is on -the machine master.kernel.org, on which I was given an account +the machine $some.kernel.org, on which I was given an account when I took over git maintainership from Linus. The directories relevant to this how-to are these two: @@ -63,7 +63,7 @@ like this: EOF $ chmod +x /pub/scm/git/git.git/hooks/post-update -There are three things worth mentioning: +There are four things worth mentioning: - The update-hook is run after the repository accepts a "git push", under my user privilege. It is given the full names @@ -77,6 +77,10 @@ There are three things worth mentioning: pull" it does into $HOME/doc-git/docgen/ repository would not work correctly. + - The stdout of update hook script is not connected to git + push; I run the heavy part of the command inside "at", to + receive the execution report via e-mail. + - This is still crude and does not protect against simultaneous make invocations stomping on each other. I would need to add some locking mechanism for this. |