[
https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464648#comment-17464648
]
Ralph Goers commented on LOG4J2-3272:
-------------------------------------
[https://gitbox.apache.org/repos/asf] shows all Git repos owned by projects.
The apache/log4j repo is not on that list. My understanding is that
apache/log4j is a mirror of
[https://svn.apache.org/repos/asf/logging/log4j/trunk/] using an older
mirroring system. It is just easier not to mess with that. Creating a clone of
the repo under the Logging Services project is just simple to do and populating
it from that Git repo was easy. The idea that that is what people are familiar
with seems far-fetched since
[https://logging.apache.org/log4j/1.2/source-repository.html] has always
pointed exclusively to SVN. The only thing lost in this is 14 PRs which can be
reviewed and migrated if necessary.
> 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
> Assignee: Ralph Goers
> 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)
