Re: [VOTE] Future of Log4j 1.x

2022-01-04 Thread Davyd McColl
+1, option 1 Apologies for the delay, took me a while to find the original email. -d On December 29, 2021 21:33:35 "Christian Grobmeier" wrote: Hello, as discussed in another thread, this is a vote about the future of log4j 1. This vote stays open for the usual 72h. Options are explain

Re: [VOTE] Future of Log4j 1.x

2022-01-04 Thread Dominik Psenner
+1, option 1 -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Tue, Jan 4, 2022, 22:19 Remko Popma wrote: > +1 for Option 1 > > On Wed, Jan 5, 2022 at 4:51 AM Volkan Yazıcı wrote: > > > +1, Option 1 > > > > On Wed, 29 Dec 2021, 20:33 Christian Grobmeier > > w

Re: [VOTE] Future of Log4j 1.x

2022-01-04 Thread Remko Popma
+1 for Option 1 On Wed, Jan 5, 2022 at 4:51 AM Volkan Yazıcı wrote: > +1, Option 1 > > On Wed, 29 Dec 2021, 20:33 Christian Grobmeier > wrote: > > > Hello, > > > > as discussed in another thread, this is a vote about the future of log4j > > 1. This vote stays open for the usual 72h. > > Options

Re: [VOTE] Future of Log4j 1.x

2022-01-04 Thread Volkan Yazıcı
+1, Option 1 On Wed, 29 Dec 2021, 20:33 Christian Grobmeier wrote: > Hello, > > as discussed in another thread, this is a vote about the future of log4j > 1. This vote stays open for the usual 72h. > Options are explained below. > > You can vote for: > > [ ] +1, Option 1 > [ ] +1, Option 2 >

Re: [log4cxx] next_stable and other fixes

2022-01-04 Thread Thorsten Schöning
Guten Tag Stephen Webb, am Dienstag, 4. Januar 2022 um 04:51 schrieben Sie: > Once the branches diverge, git cherry-pick is the better merge process. They have diverged already and all changes from master were decided to be useful in next_stable. So the results of cherry-picking and merging would