From: Martin Dummer <martin.dummer@gmx.net>
To: gentoo-dev@lists.gentoo.org, "Michał Górny" <mgorny@gentoo.org>,
gentoo-dev-announce@lists.gentoo.org
Subject: Re: [gentoo-dev] Imminent Python 3.12 switch reminder
Date: Wed, 29 May 2024 11:30:10 +0200 [thread overview]
Message-ID: <c2f4bb5d-7183-4c67-a950-80693ef9e6b7@gmx.net> (raw)
In-Reply-To: <f1a2d0862bac2d42d7f3a13ac985a790d321fe2e.camel@gentoo.org>
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
next prev parent reply other threads:[~2024-05-29 9:35 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 [this message]
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
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=c2f4bb5d-7183-4c67-a950-80693ef9e6b7@gmx.net \
--to=martin.dummer@gmx.net \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@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