From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Need help: Many patches for unmaintained packages
Date: Fri, 31 Dec 2021 14:03:45 -0500 [thread overview]
Message-ID: <Yc9UEVMfwYfA+UKZ@eversor> (raw)
In-Reply-To: <ececc7c8-6d4b-ce0c-eba6-4cc01f791b1e@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
On Fri, Dec 31, 2021 at 07:27:28PM +0100, Martin Dummer wrote:
> Am 31.12.21 um 06:51 schrieb Jonas Stein:
> > I prepared a public Bugzilla filter "m-n PATCH"
> >
> > https://bugs.gentoo.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=m-n%20PATCH&sharer_id=85842
> >
>
> Hello Jonas,
>
> when I try to open that link I receive an error message
>
> "The search named /m-n PATCH/ has not been made visible to you."
>
> Can you check the settings again please?
Seems fine on my end although I see "shared to bz_canusewhineatothers"
rather than "saved-searches" group. Probably has something to do with
it for non-devs.
Alternatively you can do a normal quick search with:
"assignee:maintainer-needed@gentoo.org kw:PATCH"[1]
Although jstein's command seem to omit the rather old bugs (seems to
limit >2019 or so), so you'll get different results with just that.
On another note, hope this will serve as a reminder for people to
add the PATCH keyword (although pull requests are still more likely
to see attention for a maintainer-needed package).
[1] https://bugs.gentoo.org/buglist.cgi?quicksearch=assignee%3Amaintainer-needed%40gentoo.org%20kw%3APATCH
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-12-31 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 5:51 [gentoo-dev] Need help: Many patches for unmaintained packages Jonas Stein
2021-12-31 18:27 ` Martin Dummer
2021-12-31 19:03 ` Ionen Wolkens [this message]
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=Yc9UEVMfwYfA+UKZ@eversor \
--to=ionen@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