Clarify that git-update-server-info should be run for every git-push
The old text suggested that git-update-server-info only needs to be run if new tags or branches are created, but not for new commits. Signed-off-by: Pavel Roskin <proski@gnu.org> Signed-off-by: Junio C Hamano <junkio@cox.net>
Pavel Roskin committed
Feb 13, 2007 at 00:43 UTC
ccf5aa8dd3bc64837a4ca391d0b8bd0e3e481b7e
1 file changed
+8
-8
Documentation/repository-layout.txt
+8
-8
@@ -133,14 +133,14 @@ info::
133
in this directory.
134
135
info/refs::
136
- This file is to help dumb transports to discover what
137
- refs are available in this repository. Whenever you
138
- create/delete a new branch or a new tag, `git
139
- update-server-info` should be run to keep this file
140
- up-to-date if the repository is published for dumb
141
- transports. The `git-receive-pack` command, which is
142
- run on a remote repository when you `git push` into it,
143
- runs `hooks/update` hook to help you achieve this.
136
+ This file helps dumb transports discover what refs are
137
+ available in this repository. If the repository is
138
+ published for dumb transports, this file should be
139
+ regenerated by `git update-server-info` every time a tag
140
+ or branch is created or modified. This is normally done
141
+ from the `hooks/update` hook, which is run by the
142
+ `git-receive-pack` command when you `git push` into the
143
+ repository.
144
145
info/grafts::
146
This file records fake commit ancestry information, to