From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: pam 1.2.1
Date: Mon, 09 Nov 2015 18:35:38 +0000 [thread overview]
Message-ID: <1447094138.2699.72.camel@ipfire.org> (raw)
In-Reply-To: <563F1B2B.9070205@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
This is probably an update that is needed. It may break many things
though. I saw that you sent a patch. You know anything about any side
-effects?
I would like to postpone this to the next Core Update since no. 95 is
rather stable now and should be released soon. This patch though should
have get a little more testing.
Best,
-Michael
On Sun, 2015-11-08 at 10:51 +0100, Matthias Fischer wrote:
> Hi,
>
> ...before I take a bite thats too big for me:
>
> Current pam-version in 'next' is 0.99.10.0, would it be of interest
> updating to the current 1.2.1?
>
> The 'Changelog' since 0.99.10.0 is rather lengthy, but I don't want
> to
> start an update thats beyond my capabilities...
>
> Regards
> Matthias
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-11-09 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 9:51 Matthias Fischer
2015-11-09 18:35 ` Michael Tremer [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=1447094138.2699.72.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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