@matheusbsbs / matheus-bagliano / commits / 3aadad1b32
Fork 0

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>

Junio C Hamano committed Dec 19, 2005 at 16:35 UTC 3aadad1b32db3555bc19dac0892d41628a8e736d
2 files changed +14 -2
Documentation/hooks.txt
+8
@@ -111,6 +111,10 @@ Another use suggested on the mailing list is to use this hook to
111 implement access control which is finer grained than the one
112 based on filesystem group.
113
114 +The standard output of this hook is sent to /dev/null; if you
115 +want to report something to the git-send-pack on the other end,
116 +you can redirect your output to your stderr.
117 +
118 post-update
119 -----------
120
@@ -125,3 +129,7 @@ the outcome of `git-receive-pack`.
129 The default post-update hook, when enabled, runs
130 `git-update-server-info` to keep the information used by dumb
131 transport up-to-date.
132 +
133 +The standard output of this hook is sent to /dev/null; if you
134 +want to report something to the git-send-pack on the other end,
135 +you can redirect your output to your stderr.
Documentation/howto/rebuild-from-update-hook.txt
+6 -2
@@ -10,7 +10,7 @@ The pages under http://www.kernel.org/pub/software/scm/git/docs/
10 are built from Documentation/ directory of the git.git project
11 and needed to be kept up-to-date. The www.kernel.org/ servers
12 are mirrored and I was told that the origin of the mirror is on
13 -the machine master.kernel.org, on which I was given an account
13 +the machine $some.kernel.org, on which I was given an account
14 when I took over git maintainership from Linus.
15
16 The directories relevant to this how-to are these two:
@@ -63,7 +63,7 @@ like this:
63 EOF
64 $ chmod +x /pub/scm/git/git.git/hooks/post-update
65
66 -There are three things worth mentioning:
66 +There are four things worth mentioning:
67
68 - The update-hook is run after the repository accepts a "git
69 push", under my user privilege. It is given the full names
@@ -77,6 +77,10 @@ There are three things worth mentioning:
77 pull" it does into $HOME/doc-git/docgen/ repository would not
78 work correctly.
79
80 + - The stdout of update hook script is not connected to git
81 + push; I run the heavy part of the command inside "at", to
82 + receive the execution report via e-mail.
83 +
84 - This is still crude and does not protect against simultaneous
85 make invocations stomping on each other. I would need to add
86 some locking mechanism for this.