I like this idea, Piotr. > On Jan 22, 2024, at 12:28 PM, Piotr P. Karwasz <piotr.karw...@gmail.com> > wrote: > > Hi Volkan, > > On Mon, 22 Jan 2024 at 15:15, Volkan Yazıcı <vol...@yazi.ci> wrote: >> Shall we mention this issue (that is, ineffective configurations as the one >> you shared about `bufferSize`-vs-`bufferedIo`) to Łukasz and see if he >> would be willing to carry out that clean up? ... granted PMC agrees to >> raise the default status logger level to WARN. > > The task to silence excessively verbose warnings can require quite a > lot of knowledge of Log4j code internals. > I prefer to do it myself and ask another PMC member to proofread it. > > Piotr
- [log4j] Bump default status logger level to WARN Piotr P. Karwasz
- Re: [log4j] Bump default status logger level to WARN Gary Gregory
- Re: [log4j] Bump default status logger level to WARN Volkan Yazıcı
- Re: [log4j] Bump default status logger level to ... Piotr P. Karwasz
- Re: [log4j] Bump default status logger level... Volkan Yazıcı
- Re: [log4j] Bump default status logger l... Piotr P. Karwasz
- Re: [log4j] Bump default status log... Matt Sicker
- RE: [log4j] Bump default status logger level to WARN Lukasz S.
- Re: [log4j] Bump default status logger level to ... Matt Sicker
- Re: [log4j] Bump default status logger level... Ralph Goers
- Re: [log4j] Bump default status logger l... Matt Sicker