public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 781ea9a03297ec298a35324cd94ee3f3e168e18a Date: Fri, 9 Apr 2021 12:58:14 +0000 (GMT) [thread overview] Message-ID: <20210409125814.CF648398B864@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 781ea9a03297ec298a35324cd94ee3f3e168e18a (commit) from 4ae43876bc9ed2bd5a4002952f3f4565be62d726 (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 781ea9a03297ec298a35324cd94ee3f3e168e18a Author: Martin Liska <mliska@suse.cz> Date: Fri Apr 9 14:58:04 2021 +0200 Add newlines before <code>. diff --git a/htdocs/branch-closing.html b/htdocs/branch-closing.html index d9c18c44..2f887b6b 100644 --- a/htdocs/branch-closing.html +++ b/htdocs/branch-closing.html @@ -56,10 +56,10 @@ closed, set it to the version number of the next release from the next oldest release branch. The step can be done by <code>maintainer-scripts/branch_changer.py</code> script -with the following arguments: +with the following arguments:<br/> <code>./branch_changer.py api_key --new-target-milestone=8.5:9.4 --remove 8 --comment 'GCC 8 branch is being closed.'</code> - +<br/> The script invocation changes target milestone from 8.5 to 9.4 and removes '/8' from a '[Regression x/y/z]' summary line. Moreover, a new comment is added. diff --git a/htdocs/releasing.html b/htdocs/releasing.html index 89f342b3..df6b93dc 100644 --- a/htdocs/releasing.html +++ b/htdocs/releasing.html @@ -146,8 +146,10 @@ Please do <strong>not</strong> delete old target milestones.</li> at either the mainline version milestone, or the next point-release milestone. This can be accomplished by <code>maintainer-scripts/branch_changer.py</code> script with the following arguments: +<br/> <code>./maintainer-scripts/branch_changer.py api_key --new-target-milestone=10.4:10.5 --comment 'GCC 10.4 is being released, retargeting bugs to GCC 10.5.'</code> +<br/> The script invocation changes target milestone from 10.4 to 10.5 and new comment <i>GCC 10.4 is being released, retargeting bugs to GCC 10.5.</i> is added. @@ -157,7 +159,9 @@ Unless you add <strong>--doit</strong>, the script runs in dry mode only. One ca <li>If you release a first branch release (e.g. 11.1.0), bug regression summary needs to adjusted by <code>maintainer-scripts/branch_changer.py</code> with the following arguments: +<br/> <code>./maintainer-scripts/branch_changer.py api_key --add=11:12</code> +<br/> The script adds '/12' to all PRs marked with a '[Regression x/y/z]' summary line. ----------------------------------------------------------------------- Summary of changes: htdocs/branch-closing.html | 4 ++-- htdocs/releasing.html | 4 ++++ 2 files changed, 6 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-04-09 12:58 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=20210409125814.CF648398B864@sourceware.org \ --to=marxin@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).