I should also note that naming a fork “relog4j” is confusingly similar to “log4j”. Please don’t infringe the trademark. -- Matt Sicker
> On Jan 6, 2022, at 18:18, Ceki Gülcü <[email protected]> wrote: > > > > Hello all, > > Given the recent refusal to even consider work on a 1.2.18 branch, which > would have been subject to PMC vote before release anyway, I have created a > separate repository on github under the name "relog4j1". The intent of > relog4j1 is to fix existing critical issues in log4j 1.x. > > If one day the logging PMC changes its mind and decides to integrate > "relog4j1" as log4j 1.x, the door is open. > > Those interested to contribute, please contact me directly. > > Good luck and thanks for the fish. > -- > Ceki Gülcü > > > On 07/01/2022 00:25, Ceki Gülcü wrote: >> On 07/01/2022 00:05, Ralph Goers wrote: >>> Unless you can convince Gary to rescind his veto there is no choice but to >>> revert. >> Reverted in github.
