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. e89d06aa560d1d36709ae7311ef2b9c74efc7f74
Date: Thu, 23 Jan 2020 21:14:00 -0000	[thread overview]
Message-ID: <20200123211442.112174.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  e89d06aa560d1d36709ae7311ef2b9c74efc7f74 (commit)
      from  1cda7199f758776f7a19638af8e0a9d3edfef193 (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 e89d06aa560d1d36709ae7311ef2b9c74efc7f74
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Thu Jan 23 21:55:06 2020 +0100

    Fix markup of &gt (to &gt;).

diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
index 047c139f..ad073b53 100644
--- a/htdocs/gitwrite.html
+++ b/htdocs/gitwrite.html
@@ -497,7 +497,7 @@ to that vendor's branches.</p>
 <p>If you have set up push access, then the branch can similarly be pushed to
   using:</p>
 <blockquote><pre>
-    git push vendors/&lt;vendor&gt; &lt;vendor&gt/&lt;topic&gt;
+    git push vendors/&lt;vendor&gt; &lt;vendor&gt;/&lt;topic&gt;
 </pre></blockquote>
 
 <p>The script can be re-run with, or without <code>--enable-push</code>
@@ -516,7 +516,7 @@ to that vendor's branches.</p>
   run and starting from the most recent commit on <code>master</code>:</p>
 
 <blockquote><pre>
-    contrib/git-add-vendor-branch.sh  &lt;vendor&gt/&lt;topic&gt; master
+    contrib/git-add-vendor-branch.sh  &lt;vendor&gt;/&lt;topic&gt; master
 </pre></blockquote>
 
 This will create the branch both locally and on the server, but will not

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gitwrite.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-01-23 21:14 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=20200123211442.112174.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: link
Be 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).