Pavel Roskin <proski@xxxxxxx> writes: > Hello! > > It looks like that either the documentation is misleading or git is not > working as promised. > > Documentation/repository-layout.txt says: > > 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. > > My understanding of the above text is that git-update-server-info only > needs to be run if a new branch or tag is created, not on every > git-push. Just because hooks/update is run on every push, it doesn't > mean that it needs to be done every time. I agree the above can be interpreted as such, and documentation updates is needed. The information in info/refs are used in full, not just the list of ref names on the far right of each line but also the object name at the beginning of each line. > I understand that accessing one file could be faster over http, so I > tend to think that it's the documentation needs to be fixed. If that's > the case, maybe hooks/update should be created executable by default? The repository that serve things over http are _minorities_, so I do not think that is a good idea. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html