From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: keywording/
Date: Wed, 30 Jul 2025 07:59:53 +0000 (UTC) [thread overview]
Message-ID: <1753862373.9af9104b263e9f98ec766a5c1b31fade20cb37a9.ulm@gentoo> (raw)
commit: 9af9104b263e9f98ec766a5c1b31fade20cb37a9
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 25 15:38:21 2025 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Jul 30 07:59:33 2025 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=9af9104b
keywording: mention pkgdev bugs for stabilization requests
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index 0cbe95e..3e51776 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -502,6 +502,11 @@ There are several tools available that can help with this:
Use <c>pkgcheck</c>'s <c>StableRequest</c> check, e.g.
<c>grep -ri "larry@" */*/metadata.xml -l | cut -d'/' -f1-2 | xargs pkgcheck scan -k StableRequest</c>
</li>
+ <li>
+ Use <c>pkgdev bugs</c> for finding and filing stabilization bugs, e.g.
+ <c>pkgdev bugs --edit-graph --filter-stablereqs
+ --auto-cc-arches larry@gentoo.org --find-by-maintainer larry@gentoo.org</c>
+ </li>
</ul>
</body>
next reply other threads:[~2025-07-30 8:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 7:59 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-30 7:59 [gentoo-commits] proj/devmanual:master commit in: keywording/ Ulrich Müller
2025-07-30 7:59 Ulrich Müller
2022-03-16 14:52 Sam James
2022-03-14 17:07 Matt Turner
2022-03-10 23:33 Sam James
2022-02-18 18:19 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2021-10-13 13:42 Ulrich Müller
2021-10-13 13:42 Ulrich Müller
2021-07-16 9:11 Ulrich Müller
2021-07-03 16:21 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-11 13:16 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-15 7:21 Ulrich Müller
2020-07-12 18:32 Ulrich Müller
2020-05-06 7:49 Ulrich Müller
2020-01-25 6:02 Ulrich Müller
2020-01-23 13:50 Ulrich Müller
2018-08-27 15:24 Göktürk Yüksek
2015-06-17 12:05 Ulrich Müller
2015-03-14 9:20 Markos Chandras
2013-02-16 0:03 Markos Chandras
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=1753862373.9af9104b263e9f98ec766a5c1b31fade20cb37a9.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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