Displaying 3 results from an estimated 3 matches for "opt_cod".
Did you mean:
opt_code
2009 Sep 05
2
[LLVMdev] code analysis bug
...uot;
" export %1$s_${OPT_NAME}${OPT_ELEMENT}\n"
" fi\n"
"done\n\n"
"unset OPT_PROCESS || :\n"
"unset OPT_ELEMENT || :\n"
"unset OPT_ARG || :\n"
"unset OPT_ARG_NEEDED || :\n"
"unset OPT_NAME || :\n"
"unset OPT_CODE || :\n"
"unset OPT_ARG_VAL || :\n%2$s";
2017 Apr 12
3
v2.2.29.1 released
https://dovecot.org/releases/2.2/dovecot-2.2.29.1.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.29.1.tar.gz.sig
Mainly because I had missed one cherry-pick from the release, which caused unit tests to also fail. And I didn't notice that, because make distcheck had been broken for some years now when it ran clang static analyzer, although I had assumed it would have run make check
2017 Apr 12
3
v2.2.29.1 released
https://dovecot.org/releases/2.2/dovecot-2.2.29.1.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.29.1.tar.gz.sig
Mainly because I had missed one cherry-pick from the release, which caused unit tests to also fail. And I didn't notice that, because make distcheck had been broken for some years now when it ran clang static analyzer, although I had assumed it would have run make check