diff options
author | Pavel Roskin <proski@gnu.org> | 2007-02-13 00:43:44 -0500 |
---|---|---|
committer | Junio C Hamano <junkio@cox.net> | 2007-02-12 22:00:45 -0800 |
commit | ccf5aa8dd3bc64837a4ca391d0b8bd0e3e481b7e (patch) | |
tree | 55b8129a0295ffd8a1a24d8e9ee1d41de5160cfc | |
parent | blameview: Move the commit info to a pane below the blame window. (diff) | |
download | tgif-ccf5aa8dd3bc64837a4ca391d0b8bd0e3e481b7e.tar.xz |
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>
-rw-r--r-- | Documentation/repository-layout.txt | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/Documentation/repository-layout.txt b/Documentation/repository-layout.txt index 863cb6710a..0459bd9ca1 100644 --- a/Documentation/repository-layout.txt +++ b/Documentation/repository-layout.txt @@ -133,14 +133,14 @@ info:: in this directory. info/refs:: - This file is to help dumb transports to discover what - refs are available in this repository. Whenever you - create/delete a new branch or a new tag, `git - update-server-info` should be run to keep this file - up-to-date if the repository is published for dumb - transports. The `git-receive-pack` command, which is - run on a remote repository when you `git push` into it, - runs `hooks/update` hook to help you achieve this. + This file helps dumb transports discover what refs are + available in this repository. If the repository is + published for dumb transports, this file should be + regenerated by `git update-server-info` every time a tag + or branch is created or modified. This is normally done + from the `hooks/update` hook, which is run by the + `git-receive-pack` command when you `git push` into the + repository. info/grafts:: This file records fake commit ancestry information, to |