On Sun, Apr 25, 2010 at 8:56 AM, William A. Rowe Jr.
wr...@rowe-clan.net wrote:
Going over the blockers to 2.0, here seem to be our choices since nobody
appears
to have the time or interest in ensuring apr_ldap becomes fully modular;
[X] Abandon apr_ldap_* API's to httpd 2.3 ldap,
On Sun, Apr 25, 2010 at 10:56:04AM -0500, William Rowe wrote:
Going over the blockers to 2.0, here seem to be our choices since nobody
appears
to have the time or interest in ensuring apr_ldap becomes fully modular;
[X] Abandon apr_ldap_* API's to httpd 2.3 ldap, including required
On Sun, Apr 25, 2010 at 11:56 AM, William A. Rowe Jr.
wr...@rowe-clan.net wrote:
Going over the blockers to 2.0, here seem to be our choices since nobody
appears
to have the time or interest in ensuring apr_ldap becomes fully modular;
[X] Abandon apr_ldap_* API's to httpd 2.3 ldap, including
Going over the blockers to 2.0, here seem to be our choices since nobody appears
to have the time or interest in ensuring apr_ldap becomes fully modular;
[ ] Abandon apr_ldap_* API's to httpd 2.3 ldap, including required autoconf
[ ] Keep apr_ldap_* within apr project, as an independent
On 4/25/2010 10:56 AM, William A. Rowe Jr. wrote:
Going over the blockers to 2.0, here seem to be our choices since nobody
appears
to have the time or interest in ensuring apr_ldap becomes fully modular;
[X] Abandon apr_ldap_* API's to httpd 2.3 ldap, including required autoconf
[ ]
