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. 6b788fa278b4f863a17ab80e0bf4991c3d8de167 Date: Mon, 19 Apr 2021 12:56:18 +0000 (GMT) [thread overview] Message-ID: <20210419125618.2401D3968C36@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 6b788fa278b4f863a17ab80e0bf4991c3d8de167 (commit) from 58d5405b469b0bc67d2c763778447f883d4f640d (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 6b788fa278b4f863a17ab80e0bf4991c3d8de167 Author: Martin Liska <mliska@suse.cz> Date: Mon Apr 19 14:55:54 2021 +0200 Move branch_changer.py usage to branching.html. diff --git a/htdocs/branching.html b/htdocs/branching.html index a9dafdd3..f30a47e1 100644 --- a/htdocs/branching.html +++ b/htdocs/branching.html @@ -97,9 +97,15 @@ delete old target milestones.</li> release on the branch. For example, when branching 3.4, create a milestone for 3.4.1 for PRs that can't be fixed in time for 3.4.0.</li> -<li>Ask Daniel Berlin to adjust all PRs with the just-branched version -in their summary to also contain the new version corresponding to -mainline.</li> +<li>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. + +Again, unless you add <strong>--doit</strong>, the script runs in dry mode only. +</li> </ol> </body> diff --git a/htdocs/releasing.html b/htdocs/releasing.html index df6b93dc..d51d6fc7 100644 --- a/htdocs/releasing.html +++ b/htdocs/releasing.html @@ -157,17 +157,6 @@ The script invocation changes target milestone from 10.4 to 10.5 and new comment Unless you add <strong>--doit</strong>, the script runs in dry mode only. One can use <code>--limit N</code> in order to limit the number of affected bugs. -<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. - -Again, unless you add <strong>--doit</strong>, the script runs in dry mode only. -</li> - <li>Update the bug searches on the main web page for the milestone changes.</li> </ol> ----------------------------------------------------------------------- Summary of changes: htdocs/branching.html | 12 +++++++++--- htdocs/releasing.html | 11 ----------- 2 files changed, 9 insertions(+), 14 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-04-19 12:56 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=20210419125618.2401D3968C36@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).