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. 2191bb87daaccd448eb21d5e38ab8263cc68b828
Date: Wed, 11 May 2022 20:55:27 +0000 (GMT)	[thread overview]
Message-ID: <20220511205527.4FFAF383642E@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  2191bb87daaccd448eb21d5e38ab8263cc68b828 (commit)
      from  9a7f570f74531be03cdd1079d6f38ccaf2be9702 (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 2191bb87daaccd448eb21d5e38ab8263cc68b828
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Wed May 11 22:55:08 2022 +0200

    branching: Remove stray </code>

diff --git a/htdocs/branching.html b/htdocs/branching.html
index bf42adf3..d3d26ff9 100644
--- a/htdocs/branching.html
+++ b/htdocs/branching.html
@@ -103,7 +103,7 @@ milestone for 3.4.1 for PRs that can't be fixed in time for 3.4.0.</li>
 <li>Bug regression summary needs to adjusted by <code>maintainer-scripts/branch_changer.py</code> with the following arguments:
 
 <blockquote><pre>
-./maintainer-scripts/branch_changer.py api_key --add=11:12</code>
+./maintainer-scripts/branch_changer.py api_key --add=11:12
 </pre></blockquote>
 
 The script adds '/12' to all PRs marked with a '[Regression x/y/z]' summary line.

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

Summary of changes:
 htdocs/branching.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2022-05-11 20:55 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=20220511205527.4FFAF383642E@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: 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).