/usr/share/doc/git/howto
NameSizeModeActions
coordinate-embargoed-releases.html298380644editdlrm
coordinate-embargoed-releases.txt108230644editdlrm
keep-canonical-history-correct.html262490644editdlrm
keep-canonical-history-correct.txt67950644editdlrm
maintain-git.html417320644editdlrm
maintain-git.txt182200644editdlrm
new-command.html220010644editdlrm
new-command.txt44600644editdlrm
rebase-from-internal-branch.html244560644editdlrm
rebase-from-internal-branch.txt63100644editdlrm
rebuild-from-update-hook.html203870644editdlrm
rebuild-from-update-hook.txt31370644editdlrm
recover-corrupted-blob-object.html238840644editdlrm
recover-corrupted-blob-object.txt55100644editdlrm
recover-corrupted-object-harder.html360380644editdlrm
recover-corrupted-object-harder.txt146070644editdlrm
revert-a-faulty-merge.html308650644editdlrm
revert-a-faulty-merge.txt108560644editdlrm
revert-branch-rebase.html247400644editdlrm
revert-branch-rebase.txt78230644editdlrm
separating-topic-branches.html205260644editdlrm
separating-topic-branches.txt33560644editdlrm
setup-git-server-over-http.html305620644editdlrm
setup-git-server-over-http.txt86130644editdlrm
update-hook-example.html232720644editdlrm
update-hook-example.txt62890644editdlrm
use-git-daemon.html196490644editdlrm
use-git-daemon.txt21350644editdlrm
using-merge-subtree.html202350644editdlrm
using-merge-subtree.txt30250644editdlrm
using-signed-tag-in-pull-request.html267650644editdlrm
using-signed-tag-in-pull-request.txt82820644editdlrm
Edit: /usr/share/doc/git/howto/rebuild-from-update-hook.html (20387B)
How to rebuild from update hook

The pages under https://www.kernel.org/pub/software/scm/git/docs/ are built from Documentation/ directory of the git.git project and needed to be kept up-to-date. The www.kernel.org/ servers are mirrored and I was told that the origin of the mirror is on the machine $some.kernel.org, on which I was given an account when I took over Git maintainership from Linus.

The directories relevant to this how-to are these two:

/pub/scm/git/git.git/       The public Git repository.
/pub/software/scm/git/docs/ The HTML documentation page.

So I made a repository to generate the documentation under my home directory over there.

$ cd
$ mkdir doc-git && cd doc-git
$ git clone /pub/scm/git/git.git/ docgen

What needs to happen is to update the $HOME/doc-git/docgen/ working tree, build HTML docs there and install the result in /pub/software/scm/git/docs/ directory. So I wrote a little script:

$ cat >dododoc.sh <<\EOF
#!/bin/sh
cd $HOME/doc-git/docgen || exit
unset GIT_DIR
git pull /pub/scm/git/git.git/ master &&
cd Documentation &&
make install-webdoc
EOF

Initially I used to run this by hand whenever I push into the public Git repository. Then I did a cron job that ran twice a day. The current round uses the post-update hook mechanism, like this:

$ cat >/pub/scm/git/git.git/hooks/post-update <<\EOF
#!/bin/sh
#
# An example hook script to prepare a packed repository for use over
# dumb transports.
#
# To enable this hook, make this file executable by "chmod +x post-update".
case " $* " in
*' refs/heads/master '*)
        echo $HOME/doc-git/dododoc.sh | at now
        ;;
esac
exec git-update-server-info
EOF
$ chmod +x /pub/scm/git/git.git/hooks/post-update

There are four things worth mentioning:

  • The update-hook is run after the repository accepts a "git push", under my user privilege. It is given the full names of refs that have been updated as arguments. My post-update runs the dododoc.sh script only when the master head is updated.

  • When update-hook is run, GIT_DIR is set to . by the calling receive-pack. This is inherited by the dododoc.sh run via the "at" command, and needs to be unset; otherwise, "git pull" it does into $HOME/doc-git/docgen/ repository would not work correctly.

  • The stdout of update hook script is not connected to git push; I run the heavy part of the command inside "at", to receive the execution report via e-mail.

  • This is still crude and does not protect against simultaneous make invocations stomping on each other. I would need to add some locking mechanism for this.