public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@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 22:53:15 +0000	[thread overview]
Message-ID: <F73CC0ED-6B0A-4FC0-B851-5CBFDDD2D118@gentoo.org> (raw)
In-Reply-To: <8d6a988a-306b-9607-a60c-803e475afd03@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]



> On 12 Dec 2022, at 22:26, Piotr Karbowski <slashbeast@gentoo.org> wrote:
> 
> 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'm not trying to challenge or come on strong on anything. I'm just saying it was unexpected?

> 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.
> 

There is nothing tactical here, we discussed it in #gentoo-base, and you're free to ask to join if you want?

(It was not instead of you doing anything, it was just something I'd been planning on anyway, but
prompted by your email like the commit message said.)

I definitely never gave you pushback like that.


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]

  reply	other threads:[~2022-12-12 22:53 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
2022-12-12 22:53         ` Sam James [this message]
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=F73CC0ED-6B0A-4FC0-B851-5CBFDDD2D118@gentoo.org \
    --to=sam@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