-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/05/2009 04:51 AM, Jakub Hrozek wrote:
> On 08/04/2009 09:17 PM, Stephen Gallagher wrote:
>> Patch 1: Ack.
>
>> Patch 2: Nack.
>> In sss_groupadd.c, sss_groupdel.c and sss_groupmod.c:
>> if (data->domain && data->uid && data->domain != dom) {
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/05/2009 04:51 AM, Jakub Hrozek wrote:
> On 08/04/2009 09:17 PM, Stephen Gallagher wrote:
>> Patch 1: Ack.
>
>> Patch 2: Nack.
>> In sss_groupadd.c, sss_groupdel.c and sss_groupmod.c:
>> if (data->domain && data->uid && data->domain != dom) {
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/04/2009 09:17 PM, Stephen Gallagher wrote:
> Patch 1: Ack.
>
> Patch 2: Nack.
> In sss_groupadd.c, sss_groupdel.c and sss_groupmod.c:
> if (data->domain && data->uid && data->domain != dom) {
> should be data->gid instead.
Thanks, I really need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/01/2009 11:27 AM, Jakub Hrozek wrote:
> Hello,
> Attached are two patches that allow the tools to operate on fully
> qualified names, that is, names in the form of u...@domain.
>
> [PATCH 1/2] Move parsing of names and domains into util/
> I use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Attached are two patches that allow the tools to operate on fully
qualified names, that is, names in the form of u...@domain.
[PATCH 1/2] Move parsing of names and domains into util/
I used the already existing facility for parsing names from t
