From: Piotr Karbowski <slashbeast@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pam: thoughts on modernizing pam_limits configuration that Gentoo ships with
Date: Mon, 12 Dec 2022 23:26:32 +0100 [thread overview]
Message-ID: <8d6a988a-306b-9607-a60c-803e475afd03@gentoo.org> (raw)
In-Reply-To: <72F4733E-9114-4F09-A385-78EFAF3A1E0B@gentoo.org>
On 12/12/2022 23.06, Sam James wrote:
> It's unusual to have discussion about a single package on the mailing lists. I tend to keep an eye on PAM
> bugs because I maintained pambase.
>
> Bugs are the primary method of discussing changes to packages.
You really came strong on this one. I did explain why it went to mailing
list, that very few people would notice bug on undeclared
maintainer-needed package, unlike mailing list, assigning it to zlogene
and hoping for few people to catch it up, yet you still zealously
challenge it.
I feel really burnt out from this exchange and I see that you already
base-system'd the sys-libs/pam tactically preventing me joining and
introducing changes, last time I wanted join base-system there was push
back and I was informed that only invited members can join. Do your
thing Sam, I will step back now and will take note to throw ideas into
void of bugzilla next time.
-- Piotr.
next prev parent reply other threads:[~2022-12-12 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 8:28 [gentoo-dev] pam: thoughts on modernizing pam_limits configuration that Gentoo ships with Piotr Karbowski
2022-12-11 12:46 ` Sam James
2022-12-11 15:38 ` Piotr Karbowski
2022-12-12 5:52 ` Robin H. Johnson
2022-12-12 21:55 ` Piotr Karbowski
2022-12-12 22:06 ` Sam James
2022-12-12 22:26 ` Piotr Karbowski [this message]
2022-12-12 22:53 ` Sam James
2022-12-13 3:24 ` John Helmert III
2022-12-13 5:18 ` Joonas Niilola
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=8d6a988a-306b-9607-a60c-803e475afd03@gentoo.org \
--to=slashbeast@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