From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Imminent Python 3.12 switch reminder
Date: Thu, 30 May 2024 18:00:45 +0200 [thread overview]
Message-ID: <0f0f6ce0ac184f1e1f436631a8929ae11f8d7851.camel@gentoo.org> (raw)
In-Reply-To: <20240530085658.1fff032a@Akita>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
On Thu, 2024-05-30 at 08:56 -0700, 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?
Nothing stops you from reviewing stuff, getting it to be merge-ready,
then pinging appropriate maintainers to merge it. Nor from becoming
a developer, to the best of my knowledge. Though this attitude may
already be a red flag.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
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
2024-05-30 16:00 ` Michał Górny [this message]
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=0f0f6ce0ac184f1e1f436631a8929ae11f8d7851.camel@gentoo.org \
--to=mgorny@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