Re: Log4j2's Automatic Configuration is great, but there is a bit ambiguity (in doc)

2023-08-16 Thread Volkan Yazıcı
Hello Fumin, There is indeed plenty of room for improvement in the Log4j documentation. We will appreciate it if you can contribute these improvements in the form of a PR. Maintainers can review and, if found to be appropriate, merge your changes. Kind regards. On Mon, Aug 7, 2023 at 8:02 PM Fum

Re: Let SLF4J do the Log4j2 Message formatting as needed

2023-08-16 Thread Volkan Yazıcı
Hello Benjamin, Are you subscribed to the `dev@` mailing list? If not, you won't be able to see responses of others; just like the one from Piotr which I am sharing below. Kind regards. On Thu, Aug 10, 2023 at 6:23 PM Piotr P. Karwasz wrote: > Hi Benjamin, > > On Thu, 10 Aug 2023 at 14:45, Ben

[Log4j] Rename `master` to `main` for `logging-parent`

2023-08-16 Thread Volkan Yazıcı
Heads up: I requested in INFRA-24901 to rename the `master` branch to `main` for the `logging-parent` repository

Re: [Log4j] Rename `master` to `main` for `logging-parent`

2023-08-16 Thread Volkan Yazıcı
Done. You need to update your local clones as follows: git branch -m master main git fetch origin git branch -u origin/main main git remote set-head origin -a On Wed, Aug 16, 2023 at 10:31 PM Volkan Yazıcı wrote: > Heads up: I requested in INFRA-24901 to rename the `master` branch to > `main` f

Re: [Log4j] Rename `master` to `main` for `logging-parent`

2023-08-16 Thread Matt Sicker
Thanks for handling that! > On Aug 16, 2023, at 3:54 PM, Volkan Yazıcı wrote: > > Done. You need to update your local clones as follows: > > git branch -m master main > git fetch origin > git branch -u origin/main main > git remote set-head origin -a > > On Wed, Aug 16, 2023 at 10:31 PM Volkan