public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: gerald@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 2236b153b573964f96b7217c6191941f303e1c94 Date: Sat, 11 Jan 2020 20:08:00 -0000 [thread overview] Message-ID: <20200111200834.50741.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 "gcc-wwwdocs". The branch, master has been updated via 2236b153b573964f96b7217c6191941f303e1c94 (commit) from 92e02da76b67c705c889642429bf82eeaaae5925 (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 2236b153b573964f96b7217c6191941f303e1c94 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sat Jan 11 21:08:17 2020 +0100 Fix markup (closing <ol>). diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html index cf52e3a..94449e3 100644 --- a/htdocs/gitwrite.html +++ b/htdocs/gitwrite.html @@ -265,6 +265,7 @@ change was made. If <code>git push</code> gives an error because someone else has pushed their own changes to the same branch, do <code>git pull --rebase</code> before trying <code>git push</code> again.</li> +</ol> <hr /> <h2 id="branches">Creating and using branches</h2> ----------------------------------------------------------------------- Summary of changes: htdocs/gitwrite.html | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-11 20: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=20200111200834.50741.qmail@sourceware.org \ --to=gerald@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).