public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Tobias Burnus <burnus@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 512805afa4a8f5db215a483b84347bbe7971da8a Date: Sun, 23 May 2021 12:24:44 +0000 (GMT) [thread overview] Message-ID: <20210523122444.B13623854813@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 "gcc-wwwdocs". The branch, master has been updated via 512805afa4a8f5db215a483b84347bbe7971da8a (commit) from 5bd025d09e4761b7ffda132a0dac04d6f10e771c (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 512805afa4a8f5db215a483b84347bbe7971da8a Author: Tobias Burnus <tobias@codesourcery.com> Date: Sun May 23 14:23:39 2021 +0200 htdocs/gitwrite.html: Remove link to nonexisting '#example' * htdocs/gitwrite.html (Contents): Remove link to '#example' which does not exist. diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html index 5332e2f5..8363e70c 100644 --- a/htdocs/gitwrite.html +++ b/htdocs/gitwrite.html @@ -23,7 +23,6 @@ maintainers and significant developers.</p> <li><a href="#policies">Write access policies</a></li> <li><a href="#testing">Testing changes</a></li> <li><a href="#checkin">Checking in a change</a></li> - <li><a href="#example">Example check-in session</a></li> <li><a href="#branches">Creating and using branches</a></li> <li><a href="#vendor">Personal and Vendor branches</a></li> <li><a href="#account">Tips&Tricks around your account</a></li> ----------------------------------------------------------------------- Summary of changes: htdocs/gitwrite.html | 1 - 1 file changed, 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-05-23 12:24 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=20210523122444.B13623854813@sourceware.org \ --to=burnus@sourceware.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).