[oe] [2011.03-maintenance] Pull request for libpam

[Mats Kärrman]

> From: openembedded-devel-bounces at lists.openembedded.org [openembedded-devel-bounces at lists.openembedded.org] on behalf of Paul Menzel [paulepanter at users.sourceforge.net]
> Sent: Tuesday, December 06, 2011 3:35 PM
> To: openembedded-devel at lists.openembedded.org
> Subject: Re: [oe] [2011.03-maintenance] Pull request for libpam
> 
> Dear Mats,
> 
> 
> Am Dienstag, den 06.12.2011, 07:55 +0000 schrieb Mats Kärrman:
> > > From: openembedded-devel-bounces at lists.openembedded.org [openembedded-devel-bounces at lists.openembedded.org] on behalf of Tom Rini [tom.rini at gmail.com]
> > > Sent: Monday, December 05, 2011 8:49 PM
> > > To: openembedded-devel at lists.openembedded.org
> > > Subject: Re: [oe] [2011.03-maintenance] Pull request for libpam
> > >
> > > On Mon, Dec 5, 2011 at 9:42 AM, Mats Kärrman <Mats.Karrman at tritech.se> wrote:
> > > > Hello Tom,
> > > >
> > > > Please pull this commit from here:
> > > >
> > > > git://github.com/mkarrman/openembedded
> > > > Branch: maintenance
> > > >
> > > > Mats Kärrman (1):
> > > >      368c68a  libpam_1.1.1: remove directory preventing /var/run from being volatile.
> > >
> > > Where is this a backport from?  Thanks!
> 
> > My local project...
> > Maybe I went ahead of myself but the solution is ~equivalent to the
> > solution applied in libpam recipes of oe-core but 1.1.1 does not exist
> > there and the corresponding fix was a part of the original recipes for
> > later versions.
> 
> so why not push it to OE-classic master first?
> 

Perhaps I missed the consensus of the "Plans for OE classic future" thread?
To my understanding pull requests from "somewhere" and master will sooner-than-later die was the way to go.
Also, pushing requires write access to the repo (that I don't have) but I can send a patch to the mailing list, if you like.

BR // Mats

> 
> Thanks,
> 
> Paul
>