my comment is below: On Fri, 7 Jan 2022 at 14:23, Christian Grobmeier <[email protected]> wrote:
> Hello, > > On Fri, Jan 7, 2022, at 08:21, Ceki Gülcü wrote: > > As for infringing on the log4j trademark, I will rename the repo to > > something else, for example "re4j". > > > > As mentioned in my previous message, if the ASF decides to integrate > > "re4j" as log4j 1.x, the door is open. > > Thanks. You did not respond to my earlier question why this is so urgent > after 10 years, > but I guess we see what you are trying to do on the fork. > > If we feel this is valuable, we may vote again. Thanks for keeping that > door open. I think working on a fork is the best way at this point of time. > I want to add my thanks to Ceki as well. I would like to see log4j-v1 get one fix in version 1.2.18 which RedHat have already made for RHEL7. It's the one for the SocketServer issue. The source for this fix is out there somewhere. I did track it down some time ago but I 've forgotten where I found it. Maybe Matt knows where it is, then it could be applied to this fork. > Good luck. > > Kind regards, > Christian >
