From: Kang Kai <Kai.Kang@windriver.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: scott.a.garman@intel.com,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 00/10] works of adding packages pam support
Date: Thu, 21 Jul 2011 17:41:26 +0800 [thread overview]
Message-ID: <4E27F446.6020001@windriver.com> (raw)
In-Reply-To: <39A05AC0-9577-4EB1-83F6-DADB53725801@dominion.thruhere.net>
On 2011年07月21日 16:53, Koen Kooi wrote:
> Op 21 jul. 2011, om 10:05 heeft Kang Kai het volgende geschreven:
>
>> On 2011年07月21日 16:00, Kang Kai wrote:
>>> From: Kang Kai<kai.kang@windriver.com>
>>>
>>>
>>> Hi Scott,
>>>
>>> This is the current work of adding pam supports.
>>>
>>> After update libpam to 1.1.4, we enable the packages pam support. And if the pacakge
>>> doesn't have a pam configure file, import from Fedora.
>>>
>>> The following changes since commit fa4bcfdb73167f8159b88e5a4d711c0d37627a70:
>>>
>>> bb-matrix: correct BB and PM number canonicalization (2011-07-14 22:23:09 +0100)
>>>
>>> are available in the git repository at:
>>> git://git.pokylinux.org/poky-contrib kangkai/distro
>>>
>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/pam-commits
>> sorry, the branch info is wrong, should be
>>
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/distro
> Is that against oe-core or against poky? If it's against poky please rebase it against oe-core since that make it possible to test it.
Koen,
I rebase against oe-core and push to
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai%2Fpam-rebase-oe-core
Is that what you want?
Regards,
Kai
next prev parent reply other threads:[~2011-07-21 9:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 8:00 [PATCH 00/10] works of adding packages pam support Kang Kai
2011-07-21 8:00 ` [PATCH 01/10] libpam: update to 1.1.4 and add subpackage xtests Kang Kai
2011-07-21 8:00 ` [PATCH 02/10] dropbear: Support PAM Kang Kai
2011-07-21 8:54 ` Koen Kooi
2011-07-21 19:10 ` Khem Raj
2011-07-22 2:41 ` Kang Kai
2011-07-22 2:49 ` Khem Raj
2011-07-22 2:56 ` Kang Kai
2011-07-21 8:00 ` [PATCH 03/10] openssh: " Kang Kai
2011-07-21 8:55 ` Koen Kooi
2011-07-21 9:05 ` Phil Blundell
2011-07-21 8:00 ` [PATCH 04/10] polkit: " Kang Kai
2011-07-21 8:59 ` Koen Kooi
2011-07-21 9:49 ` Kang Kai
2011-07-21 9:59 ` Koen Kooi
2011-07-22 3:21 ` Kang Kai
2011-07-21 8:00 ` [PATCH 05/10] cups: add pam support Kang Kai
2011-07-21 8:00 ` [PATCH 06/10] screen: " Kang Kai
2011-07-21 8:00 ` [PATCH 07/10] sudo: " Kang Kai
2011-07-21 9:06 ` Phil Blundell
2011-07-21 9:42 ` Kang Kai
2011-07-21 8:00 ` [PATCH 08/10] cronie: enable PAM support for cronie Kang Kai
2011-07-21 8:00 ` [PATCH 09/10] shadow: update pam related configure files Kang Kai
2011-07-21 8:58 ` Koen Kooi
2011-07-22 3:16 ` Kang Kai
2011-07-21 8:00 ` [PATCH 10/10] at: enable pam support Kang Kai
2011-07-21 8:05 ` [PATCH 00/10] works of adding packages " Kang Kai
2011-07-21 8:53 ` Koen Kooi
2011-07-21 9:41 ` Kang Kai [this message]
2011-07-21 9:58 ` Koen Kooi
2011-07-21 17:02 ` Saul Wold
2011-07-22 2:18 ` Kang Kai
2011-07-22 3:10 ` Saul Wold
2011-07-22 3:14 ` Kang Kai
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=4E27F446.6020001@windriver.com \
--to=kai.kang@windriver.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=scott.a.garman@intel.com \
/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