-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/13/2010 09:50 AM, Stephen Gallagher wrote:
> On 10/13/2010 01:42 AM, Sumit Bose wrote:
>> On Tue, Oct 12, 2010 at 11:24:13AM -0400, Stephen Gallagher wrote:
>> On 10/12/2010 10:18 AM, Sumit Bose wrote:
> On Mon, Oct 11, 2010 at 02:32:59PM -04
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/13/2010 01:42 AM, Sumit Bose wrote:
> On Tue, Oct 12, 2010 at 11:24:13AM -0400, Stephen Gallagher wrote:
> On 10/12/2010 10:18 AM, Sumit Bose wrote:
On Mon, Oct 11, 2010 at 02:32:59PM -0400, Stephen Gallagher wrote:
Also, I'm not sure t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/12/2010 10:18 AM, Sumit Bose wrote:
> On Mon, Oct 11, 2010 at 02:32:59PM -0400, Stephen Gallagher wrote:
> Also, I'm not sure that this is safe for aligned platforms like MIPS. It
> might be wisest to just make this a 32-bit value and use the ali
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/05/2010 10:21 AM, Sumit Bose wrote:
> Hi,
>
> this series of patches continue the work Stephen has started in
> "[PATCHES] Support for netgroups in the NSS client and responder".
>
> We decided to try to be as compatible to nss_ldap as possible
On Tue, Oct 05, 2010 at 04:21:01PM +0200, Sumit Bose wrote:
> Hi,
>
> this series of patches continue the work Stephen has started in
> "[PATCHES] Support for netgroups in the NSS client and responder".
>
> We decided to try to be as compatible to nss_ldap as possible, i.e. we
> do not any group
