public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 6e86d16b187fc42700b3f1298b68dd89db02c025 Date: Sun, 31 May 2020 11:08:40 +0000 (GMT) [thread overview] Message-ID: <20200531110840.E8BB1385DC0A@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 6e86d16b187fc42700b3f1298b68dd89db02c025 (commit) from 793ea4ab70b823bd823a2c7fb34b386d31ca3137 (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 6e86d16b187fc42700b3f1298b68dd89db02c025 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sun May 31 13:06:02 2020 +0200 Update examples for branches and tags to newer ones. diff --git a/htdocs/git.html b/htdocs/git.html index bec93ead..8c28bc02 100644 --- a/htdocs/git.html +++ b/htdocs/git.html @@ -146,12 +146,12 @@ series, <em>Y</em> is always nonzero and <em>Z</em> is always zero for a release, with other version numbers being used for development versions.)</p> -<p>The following list provides some representative examples:</p> +<p>The following are some representative examples:</p> <ul> + <li>releases/gcc-10 (a branch)</li> <li>releases/gcc-9 (a branch)</li> - <li>releases/gcc-8 (a branch)</li> - <li>releases/gcc-7.5.0 (a tag)</li> + <li>releases/gcc-9.3.0 (a tag)</li> <li>releases/gcc-4.9 (a branch)</li> <li>releases/gcc-4.9.0 (a tag)</li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/git.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-05-31 11:08 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=20200531110840.E8BB1385DC0A@sourceware.org \ --to=gerald@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).