From 89afab0bed15981d91a0e1dbbb6ebd1957e7fbf0 Mon Sep 17 00:00:00 2001 From: Stephen Haberman Date: Tue, 11 Nov 2008 15:36:45 -0600 Subject: [PATCH] Prune contrib-specific docs. --- server/post-receive-email | 17 ++++------------- 1 file changed, 4 insertions(+), 13 deletions(-) diff --git a/server/post-receive-email b/server/post-receive-email index 1fdecc8..f5350ef 100755 --- a/server/post-receive-email +++ b/server/post-receive-email @@ -1,22 +1,12 @@ #!/bin/sh # # Copyright (c) 2007 Andy Parkins +# Copyright (c) 2008 Stephen Haberman # -# An example hook script to mail out commit update information. This hook -# sends emails listing new revisions to the repository introduced by the -# change being reported. The rule is that (for branch updates) each commit +# This hook sends emails listing new revisions to the repository introduced by +# the change being reported. The rule is that (for branch updates) each commit # will appear on one email and one email only. # -# This hook is stored in the contrib/hooks directory. Your distribution -# will have put this somewhere standard. You should make this script -# executable then link to it in the repository you would like to use it in. -# For example, on debian the hook is stored in -# /usr/share/doc/git-core/contrib/hooks/post-receive-email: -# -# chmod a+x post-receive-email -# cd /path/to/your/repository.git -# ln -sf /usr/share/doc/git-core/contrib/hooks/post-receive-email hooks/post-receive -# # This hook script assumes it is enabled on the central repository of a # project, with all users pushing only to it and not between each other. It # will still work if you don't operate in that style, but it would become @@ -487,3 +477,4 @@ else fi done fi + -- 2.20.1