public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pam: thoughts on modernizing pam_limits configuration that Gentoo ships with
Date: Tue, 13 Dec 2022 07:18:28 +0200	[thread overview]
Message-ID: <f9b277b2-b666-100a-b50f-0b86f2935f79@gentoo.org> (raw)
In-Reply-To: <8d6a988a-306b-9607-a60c-803e475afd03@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1203 bytes --]

On 13.12.2022 0.26, Piotr Karbowski 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 see value in having both, this mailing list discussion AND a bug. It
was indeed a great initiative to open the discussion here, since as you
said the main maintainer is AWOL and pam is a critical package so this
needs attention, but the fix should now be finished in a bug IMHO.

Once you make the changing commit you can reference a bug and it'll show
relevant history data for the reason. It's much harder and annoying
trying to locate the "why was this ever changed?" from a mailing list,
months or years after, when you can just find a commit and a linked bug.

-- juippis

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

      parent reply	other threads:[~2022-12-13  5:18 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
2022-12-13  3:24         ` John Helmert III
2022-12-13  5:18         ` Joonas Niilola [this message]

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=f9b277b2-b666-100a-b50f-0b86f2935f79@gentoo.org \
    --to=juippis@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