> On Mar 21, 2022, at 4:39 PM, Gary Gregory wrote:
>
> On Mon, Mar 21, 2022 at 7:28 PM Ralph Goers
> wrote:
>
>> Does that imply you are going to finish porting the changes to master or
>> are
>> you expecting someone else to do it?
>>
>
> I am not implying anything, I was just reporting s
On Mon, Mar 21, 2022 at 7:28 PM Ralph Goers
wrote:
> Does that imply you are going to finish porting the changes to master or
> are
> you expecting someone else to do it?
>
I am not implying anything, I was just reporting some history ;-) I have no
expectations or desire to tell others what to d
Does that imply you are going to finish porting the changes to master or are
you expecting someone else to do it?
Ralph
> On Mar 21, 2022, at 12:11 PM, Gary Gregory wrote:
>
> Yes, master is behind. At some point, both master and release-2.x,
> especially master had build problems. When I coul
Yes, master is behind. At some point, both master and release-2.x,
especially master had build problems. When I could not build master I
stopped porting changes which I had been doing all along for my 1.2 bridge
changes. I just did not want to put in even more time into master when I
had a lot left
There are lots of commits in 2.x that need to be ported to master. Now
that I've mostly finished the DI epic, I was thinking of working on
auditing 2.x commits to make sure they're in master, though I'd hope
that each of us can do that in modules we're familiar with.
On Mon, Mar 21, 2022 at 6:19 A
Gary and Piotr put a great deal of effort into `log4j-1.2-api` in
`release-2.x`. So far we haven't heard of any major complaints but happy
migration stories. Great job! 💯
While trying to cherry-pick a one-liner from `release-2.x` to `master`
today, I have run into some issues. If I am not mistaken
