aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2005-09-02 11:46:43 -0700
committerJunio C Hamano <junkio@cox.net>2005-09-02 11:46:43 -0700
commit953e5842f8fcd40c3e7013a9793746719016db1b (patch)
tree394b750a6e25c2f085d950dbe04368e212f07ad8
parent86b13da46cd710a45a89968880c691452d5b70b4 (diff)
downloadgit-953e5842f8fcd40c3e7013a9793746719016db1b.tar.gz
git-953e5842f8fcd40c3e7013a9793746719016db1b.tar.xz
Mention post-update when we first talk about publishing a repository.
There is more detailed instruction for `project lead` later in the tutorial to talk about the same, but at this point in the flow of tutorial, the first time reader has no way of knowing it. Signed-off-by: Junio C Hamano <junkio@cox.net>
-rw-r--r--Documentation/tutorial.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index 04354a37b..8d999b02d 100644
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -1103,6 +1103,12 @@ your login shell is `bash`, only `.bashrc` is read and not
`.bash_profile`. As a workaround, make sure `.bashrc` sets up
`$PATH` so that you can run `git-receive-pack` program.
+[NOTE]
+If you plan to publish this repository to be accessed over http,
+you should do `chmod +x my-git.git/hooks/post-update` at this
+point. This makes sure that every time you push into this
+repository, `git-update-server-info` is run.
+
Your "public repository" is now ready to accept your changes.
Come back to the machine you have your private repository. From
there, run this command: