On Mon, Mar 21, 2022 at 7:28 PM Ralph Goers <ralph.go...@dslextreme.com>
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 do here.
I am packing for a vacation tonight, getting on a plane, and will be back
March 29, so I might be able to keep up with some FOSS or emergency day job
issues but I hope not.
After I get back, I'll have to see. The last time I tried to take a
vacation, we got Log4Shell'd. Fingers crossed.

Gary


>
> Ralph
>
> > On Mar 21, 2022, at 12:11 PM, Gary Gregory <garydgreg...@gmail.com>
> wrote:
> >
> > 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 to do in release-2.x. So, that's how we got to where we
> are.
> >
> > Gary
> >
> > Gary
> >
> > On Mon, Mar 21, 2022, 07:19 Volkan Yazıcı <vol...@yazi.ci> wrote:
> >
> >> 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,
> `log4j-1.2-api`
> >> lags behind quite a bit in `master` compared to `release-2.x`. Is this
> >> intentional? If not, do we have any plans to sync the two?
> >>
>
>

Reply via email to