From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: About pam herd status
Date: Thu, 9 Jan 2014 15:20:59 -0500 [thread overview]
Message-ID: <201401091521.00050.vapier@gentoo.org> (raw)
In-Reply-To: <52A636D9.7050904@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 757 bytes --]
On Monday 09 December 2013 16:32:09 Markos Chandras wrote:
> On 12/09/2013 02:21 PM, Diego Elio Pettenò wrote:
> > On Mon, Dec 9, 2013 at 2:20 PM, Pacho Ramos <pacho@gentoo.org> wrote:
> >> Hello
> >>
> >> Is pam team still active? I wonder about this as, recently, we have
> >> needed to go ahead and fix some bugs related, for example, with pambase
> >> and pam_ssh
> >>
> >> Thanks for the info :)
>
> So I guess it's time to call for maintainers or we should consider
> merging this herd with another one (base?) to avoid unattended bugs for
> a long time.
well, the sep herd was kind of by design ... i didn't want it cluttering up
base-system@ and it is super convenient to abdicate all PAM decisions to a
single herd.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-09 20:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 14:20 [gentoo-dev] About pam herd status Pacho Ramos
2013-12-09 14:21 ` [gentoo-dev] " Diego Elio Pettenò
2013-12-09 14:22 ` Andreas K. Huettel
2013-12-09 21:32 ` Markos Chandras
2014-01-09 20:20 ` Mike Frysinger [this message]
2014-01-09 20:22 ` Markos Chandras
2014-01-09 20:24 ` Diego Elio Pettenò
2014-01-10 22:20 ` Mike Frysinger
2014-01-10 23:14 ` Diego Elio Pettenò
2014-01-11 10:57 ` Markos Chandras
2014-01-11 11:01 ` Pacho Ramos
2014-01-11 11:07 ` Diego Elio Pettenò
2014-01-11 11:15 ` Markos Chandras
2014-01-11 11:15 ` Pacho Ramos
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=201401091521.00050.vapier@gentoo.org \
--to=vapier@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