public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: jsm28@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: UNNAMED PROJECT branch master updated. 77b0d72a2772def18a9776549c9aee91b93a81e8 Date: Wed, 09 Oct 2019 00:07:00 -0000 [thread overview] Message-ID: <20191009000722.56625.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "UNNAMED PROJECT". The branch, master has been updated via 77b0d72a2772def18a9776549c9aee91b93a81e8 (commit) from 363192da7599480b59ad3e6a57b0e44096ba0306 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 77b0d72a2772def18a9776549c9aee91b93a81e8 Author: Joseph Myers <joseph@codesourcery.com> Date: Wed Oct 9 00:06:37 2019 +0000 Add post-receive hook for wwwdocs in git. diff --git a/bin/post-receive b/bin/post-receive new file mode 100755 index 0000000..1114efc --- /dev/null +++ b/bin/post-receive @@ -0,0 +1,55 @@ +#!/bin/bash + +# The post-receive hook receives, on standard input, a series of lines +# of the form: +# +# <old-value> SP <new-value> SP <ref-name> LF +# +# describing ref updates that have just occurred. In the case of this +# repository, only updates to refs/heads/master are expected, and only +# such updates should result in automatic website updates. + +TOP_DIR=/www/gcc + +exec >> "$TOP_DIR/updatelog" 2>&1 + +export QMAILHOST=gcc.gnu.org + +tmp=$(mktemp) +cat > "$tmp" + +# Send commit emails. Appropriate config values should be set in the +# git repository for this. +/sourceware/libre/infra/bin/post-receive-email < "$tmp" + +# Update web page checkouts, if applicable. +while read old_value new_value ref_name; do + if [ "$ref_name" != "refs/heads/master" ]; then + continue + fi + unset GIT_DIR + unset GIT_WORK_TREE + cd "$TOP_DIR/wwwdocs-checkout" + git pull --quiet + # $TOP_DIR/bin, $TOP_DIR/cgi-bin and $TOP_DIR/htdocs-preformatted + # should be symlinks into wwwdocs-checkout. + git diff --name-only "$old_value..$new_value" | while read file; do + case "$file" in + (htdocs/*) + ;; + (*) + continue + ;; + esac + dir="${file%/*}" + if ! [ -d "$TOP_DIR/$dir" ]; then + mkdir "$TOP_DIR/$dir" + chmod 2775 "$TOP_DIR/$dir" + fi + if [ -f "$file" ]; then + /www/gcc/bin/preprocess "${file#htdocs/}" + fi + done +done < "$tmp" + +rm "$tmp" ----------------------------------------------------------------------- Summary of changes: bin/post-receive | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 55 insertions(+), 0 deletions(-) create mode 100755 bin/post-receive hooks/post-receive -- UNNAMED PROJECT
reply other threads:[~2019-10-09 0:07 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20191009000722.56625.qmail@sourceware.org \ --to=jsm28@gcc.gnu.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).