public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: Pacho Ramos <pacho@gentoo.org>
Cc: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>,
	pam-bugs@gentoo.org
Subject: [gentoo-dev] Re: About pam herd status
Date: Mon, 9 Dec 2013 14:21:17 +0000	[thread overview]
Message-ID: <CAHcsgXSOJXoycrjUK1GbngwXL73RmFkQGK+q0J=dM6vLKpiMVQ@mail.gmail.com> (raw)
In-Reply-To: <1386598800.12112.7.camel@belkin5>

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

I stopped caring about pambase when people decided to break it.

I'm still officially pam herd as maintainer of Linux-PAM, pam_ssh I don't
use and care very little about.


Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/


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 :)
>
>

[-- Attachment #2: Type: text/html, Size: 1049 bytes --]

  reply	other threads:[~2013-12-09 14: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 ` Diego Elio Pettenò [this message]
2013-12-09 14:22   ` [gentoo-dev] " Andreas K. Huettel
2013-12-09 21:32   ` Markos Chandras
2014-01-09 20:20     ` Mike Frysinger
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='CAHcsgXSOJXoycrjUK1GbngwXL73RmFkQGK+q0J=dM6vLKpiMVQ@mail.gmail.com' \
    --to=flameeyes@flameeyes.eu \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=pacho@gentoo.org \
    --cc=pam-bugs@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