On Thu, 2009-08-27 at 09:55 -0400, Jenny Galipeau wrote:
> Simo Sorce wrote:
> > On Thu, 2009-08-27 at 14:33 +0200, Sumit Bose wrote:
> >
> >> On Thu, Aug 27, 2009 at 12:58:41AM -0400, Simo Sorce wrote:
> >>
> >>> The "legacy" option was introduced to speed up development.
> >>> It is actua
Simo Sorce wrote:
> On Thu, 2009-08-27 at 14:33 +0200, Sumit Bose wrote:
>
>> On Thu, Aug 27, 2009 at 12:58:41AM -0400, Simo Sorce wrote:
>>
>>> The "legacy" option was introduced to speed up development.
>>> It is actually confusing and not necessary.
>>> >From now on we store all using th
On Thu, 2009-08-27 at 14:33 +0200, Sumit Bose wrote:
> On Thu, Aug 27, 2009 at 12:58:41AM -0400, Simo Sorce wrote:
> > The "legacy" option was introduced to speed up development.
> > It is actually confusing and not necessary.
> > >From now on we store all using the member/memberof schema
> interna
On Thu, Aug 27, 2009 at 12:58:41AM -0400, Simo Sorce wrote:
> The "legacy" option was introduced to speed up development.
> It is actually confusing and not necessary.
> >From now on we store all using the member/memberof schema internally.
> (Tested only with the native ldap driver).
>
> 0001 mai
The "legacy" option was introduced to speed up development.
It is actually confusing and not necessary.
>From now on we store all using the member/memberof schema internally.
(Tested only with the native ldap driver).
0001 mainly converts the core sysdb functions
0002 fixes many errors in fill_gre
