[
https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464398#comment-17464398
]
Remko Popma edited comment on LOG4J2-3272 at 12/23/21, 10:03 AM:
-----------------------------------------------------------------
-Oh good point, we should probably make the Subversion repo read-only and point
people to this git repo.-
Sorry, the svn repo was already read-only.
Maybe the issue was that it’s not easy to make the git clone read-write while
keeping the svn repo read-only.
Anyway, Ralph announced this repo on the dev mailing list, and it’s ready for
use.
Looking forward to everyone’s contributions!
was (Author: [email protected]):
-Oh good point, we should probably make the Subversion repo read-only and point
people to this git repo. -
Sorry, the svn repo was already read-only.
Maybe the issue was that it’s not easy to make the git clone read-write while
keeping the svn repo read-only.
Anyway, Ralph announced this repo on the dev mailing list, and it’s ready for
use.
Looking forward to everyone’s contributions!
> Enable Git and GitHub for log4j 1.2 repository
> ----------------------------------------------
>
> Key: LOG4J2-3272
> URL: https://issues.apache.org/jira/browse/LOG4J2-3272
> Project: Log4j 2
> Issue Type: Task
> Reporter: Vladimir Sitnikov
> Priority: Blocker
>
> Please enable Git and GitHub for log4j 1.2 repository so it is easier to
> suggest and test changes.
> Every patch to 1.x must be well-tested, so attaching SVN patch files to JIRA
> is a recipe for disaster
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
