Re: [log4j] which branches can be deleted?

2018-02-02 Thread Ralph Goers
Obviously release-2.x needs to stay as you just created it. Master of course has to stay. I’d like to keep android around until we solve that problem. I would have to look at each of the specified Jira issues to know which can be deleted. Ralph > On Feb 2, 2018, at 1:39 AM, Remko Popma

Re: [log4j] which branches can be deleted?

2018-02-02 Thread Matt Sicker
I removed LOG4J2-1431 as it was merged. You can obviously remove master from that list as well. On 2 February 2018 at 02:39, Remko Popma wrote: > Can some of these branches be deleted? > > >git branch -r --list > origin/2.0-beta1 > origin/AutoCloseableLock >

[log4j] which branches can be deleted?

2018-02-02 Thread Remko Popma
Can some of these branches be deleted? >git branch -r --list origin/2.0-beta1 origin/AutoCloseableLock origin/GenericMapMessage origin/GenericMapMessageSimple origin/LOG4J2-1116 (Web app-friendly thread locals for gc-free logging (was: upgrade to log4j2 causes too frequent minor gc))