4 day ago, you all saw this. 6 years ago, you all started using this on trunk.
Don't know what I can to do help this along and honor the library
author's wishes for
all of us to walk away from the dead fork, and use the maintained
fork. It's whatever
it is, I'm out of here and removing the backpor
On 16 Jan 2022, at 18:54, Yann Ylavic wrote:
> Maybe "ldap_escape" would be a more appropriate name, should there be
> a need for another ldap function (e.g. "ldap_unescape") later?
This doesn’t follow the existing “short” naming pattern of the existing
entries. I image that we’d add something
On Sun, Jan 16, 2022 at 2:42 PM wrote:
>
> +Index: server/util_expr_eval.c
> +===
> +--- server/util_expr_eval.c(revision 1897120)
> server/util_expr_eval.c(working copy)
[]
> +@@ -1667,6 +1678,9 @@
> + { unbase64_fun
