From: Jaco Kroon <jaco@uls.co.za>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Imminent Python 3.12 switch reminder
Date: Thu, 30 May 2024 18:00:12 +0200 [thread overview]
Message-ID: <5315018c-eb80-4711-bc78-b37d9ad80e8f@uls.co.za> (raw)
In-Reply-To: <20240530085658.1fff032a@Akita>
On 2024/05/30 17:56, orbea wrote:
> On Thu, 30 May 2024 17:54:32 +0200
> Michał Górny <mgorny@gentoo.org> wrote:
>
>> On Thu, 2024-05-30 at 08:09 -0700, orbea wrote:
>>> This is a reoccurring theme and its driving away contributors. The
>>> PR queue really should be taken care of.
>> Talk is cheap.
>>
> If I had the power to do it myself I would of already started to try to
> reduce the load, but I don't. Do you want to grant me that power?
+1.
Realising even my own ebuilds can do with some work, but yes, as a PR
this is the part of the process that I most look up to. Even if PR
maintainers that have been around can just be given rights to commit to
their own (long maintained) packages, that would already help alleviate
the queue.
Kind regards,
Jaco
next prev parent reply other threads:[~2024-05-30 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 6:24 [gentoo-dev] Imminent Python 3.12 switch reminder Michał Górny
2024-05-29 9:30 ` Martin Dummer
2024-05-30 9:34 ` Florian Schmaus
2024-05-30 15:09 ` orbea
2024-05-30 15:54 ` Michał Górny
2024-05-30 15:56 ` orbea
2024-05-30 16:00 ` Jaco Kroon [this message]
2024-05-30 16:00 ` Michał Górny
2024-05-30 22:11 ` [gentoo-dev] Proxy-maint PR queue resolution speed (Was: Imminent Python 3.12 switch reminder) Eli Schwartz
2024-05-31 0:21 ` [gentoo-dev] Imminent Python 3.12 switch reminder Sam James
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=5315018c-eb80-4711-bc78-b37d9ad80e8f@uls.co.za \
--to=jaco@uls.co.za \
--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