[
https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464421#comment-17464421
]
Vladimir Sitnikov commented on LOG4J2-3272:
-------------------------------------------
Just in case, I do not really want to do nit-picking, I do not want or expect
you to read others' brains.
I do understand you might still have an unusual spike regarding the CVEs.
It is kind of sad and unexpected when I ask "open Git and GitHub for log4j 1.2
repository" (I mean https://github.com/apache/log4j), and what you do is
something different. At the same time, you provide no reasons why a second repo
was created instead of opening the old one.
So far I see absolutely no reason to have multiple Git/GitHub repositories for
log4j 1.2.
Thanks for the understanding, and thanks for the patience.
> 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)
