From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Martin Dummer <martin.dummer@gmx.net>
Subject: Re: [gentoo-dev] Imminent Python 3.12 switch reminder
Date: Thu, 30 May 2024 11:34:42 +0200 [thread overview]
Message-ID: <9479c6ac-bcde-45d2-87b3-c5c3b7ec88fa@gentoo.org> (raw)
In-Reply-To: <c2f4bb5d-7183-4c67-a950-80693ef9e6b7@gmx.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 543 bytes --]
On 29/05/2024 11.30, Martin Dummer wrote:
> Am 28.05.24 um 08:24 schrieb Michał Górny:
>> If you're up for some more quick porting, right now's the time!
> https://github.com/gentoo/gentoo/pull/36502 laying around for ~ 1 Month
Unfortunately it happens that proxy-maint PRs slip through the cracks.
If this happens, like it seems to have been the case with your PR, then
please ping us proxy maintainers. Ideally simply by mentioning PRs that
need attention of proxy maintainers in #gentoo-proxy-maint (Libera IRC).
- Flow
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 17797 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2024-05-30 9:34 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 [this message]
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
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=9479c6ac-bcde-45d2-87b3-c5c3b7ec88fa@gentoo.org \
--to=flow@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=martin.dummer@gmx.net \
/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