I think the current git repo is an SVN mirror, so there's no way to merge from github into SVN(as far as I can tell). I think we would have to create a new repo and make the PR against the new repo instead.
Making a new git repo is now self-serve: https://infra.apache.org/svn-to-git-migration.html The PMC chair needs to be the one to create the repo though. -Robert Middleton On Sat, Dec 18, 2021 at 11:38 AM Leo Simons <[email protected]> wrote: > > +1 from me. > > I imagine it should make it easier to make the security release when setup > for 1.2 is more similar to 2.x. > That should mean people who are good at releasing 2.x have an easy time > releasing 1.2.18. > > I think we can (and should) do this in such a way that 1.2 EOL status > becomes *more* clear to git people. > > To that end, in the case where SVN stays as the source, I think we should > still add a README.md to the trunk, so that https://github.com/apache/log4j > makes it very clear the package is EOL. > > > Cheers, > > > Leo > > On Thu, Dec 16, 2021 at 5:50 AM Vladimir Sitnikov < > [email protected]> wrote: > > > Hi, > > > > I suggest log4j 1.x moves from SVN to Git. > > I do not expect to have great development, however, moving to Git would > > make > > it easier to contribute and review changes. > > > > [ ] +1 let's move to Git and make SVN read-only > > [ ] -1 don't do that because ... > > > > Here's my vote: +1 > > > > Vladimir > >
