[
https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464414#comment-17464414
]
Vladimir Sitnikov edited comment on LOG4J2-3272 at 12/23/21, 10:16 AM:
-----------------------------------------------------------------------
{quote}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.{quote}
[~rgoers], would you please clarify?
The old repository was well-known (see watches, stars, forks), and the new one
is just blank.
{quote} Anyway, Ralph announced this repo on the dev mailing list, and it’s
ready for use.{quote}
Now there are **two** Git repositories for log4j 1.x with exactly the same code.
Would you please re-consider, drop the new "logging-log4j1", and ask INFRA to
stop svn->git mirror, and open https://github.com/apache/log4j for
contributions?
was (Author: vladimirsitnikov):
{quote}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.{quote}
[~rgoers], would you please clarify?
The old repository was well-known (see watches, stars, forks), and the new one
is just blank.
{quote} Anyway, Ralph announced this repo on the dev mailing list, and it’s
ready for use.{quote}
Now there are **two** repositories for log4j with exactly the same code.
Would you please re-consider, drop the new "logging-log4j1", and ask INFRA to
stop svn->git mirror, and open https://github.com/apache/log4j for
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
> 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)
