From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/new-ebuild/
Date: Sat, 21 Oct 2023 11:46:53 +0000 (UTC) [thread overview]
Message-ID: <1697888634.fd399e73274e120f5171d2f75fe0dfbe8c032b1d.ulm@gentoo> (raw)
commit: fd399e73274e120f5171d2f75fe0dfbe8c032b1d
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 21 11:43:54 2023 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sat Oct 21 11:43:54 2023 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=fd399e73
ebuild-maintenance/new-ebuild; Fix link to bugzilla advanced search
Also update the paragraph explaining it.
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
ebuild-maintenance/new-ebuild/text.xml | 19 ++++++++++---------
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/ebuild-maintenance/new-ebuild/text.xml b/ebuild-maintenance/new-ebuild/text.xml
index ea6dcab..10793e0 100644
--- a/ebuild-maintenance/new-ebuild/text.xml
+++ b/ebuild-maintenance/new-ebuild/text.xml
@@ -8,15 +8,16 @@
<body>
<p>
-Before writing a new ebuild, check
-<uri link="https://bugs.gentoo.org/">bugs.gentoo.org</uri>
-to see if an ebuild has already been written for the package, but has not yet
-been added to the Gentoo repository. Go to <uri
-link="https://bugs.gentoo.org/">bugs.gentoo.org</uri>, choose query and select
-Advanced Search; as product select <e>Gentoo Linux</e>, as component select
-<e>ebuilds</e>. In the search field put the name of the ebuild and as status
-select all possible fields, then submit the query. For you lazy people, click
-<uri link="https://bugs.gentoo.org/query.cgi?format=advanced&product=Gentoo%20Linux&component=New%20Ebuilds&bug_Status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED">here</uri>.
+Before writing a new ebuild, check <uri link="https://bugs.gentoo.org/">
+bugs.gentoo.org</uri> to see if an ebuild has already been written for
+the package, but has not yet been added to the Gentoo repository. Go to
+<uri link="https://bugs.gentoo.org/">bugs.gentoo.org</uri>, choose query and
+select Advanced Search; as product select <e>Gentoo Linux</e>, as component
+select <e>New packages</e>. In the search field put the name of the ebuild and
+as status and resolution select all possible fields, then submit the query.
+For you lazy people, here is a
+<uri link="https://bugs.gentoo.org/query.cgi?format=advanced&product=Gentoo%20Linux&component=New%20packages">
+Bugzilla advanced search</uri> link.
</p>
<p>
next reply other threads:[~2023-10-21 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 11:46 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-22 23:40 [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/new-ebuild/ Sam James
2021-04-07 17:35 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2020-03-02 10:49 Ulrich Müller
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=1697888634.fd399e73274e120f5171d2f75fe0dfbe8c032b1d.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