[ https://issues.apache.org/jira/browse/DERBY-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868320#comment-17868320 ]
Qiheng He commented on DERBY-7162: ---------------------------------- - Although github has abandoned support for Subversion at https://github.blog/news-insights/product-news/sunsetting-subversion-support/, I noticed that apache/subversion itself can be mirrored in real time on github, namely https://github.com/apache/subversion. - It seems that all relevant github documents have been deleted, leaving only https://docs.github.com/en/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-subversion-repository, which introduces how to convert an svn repository to a git repository. > Update Git mirror for db-derby. Current mirror is out of date, hasn't been > updated since 2019 > --------------------------------------------------------------------------------------------- > > Key: DERBY-7162 > URL: https://issues.apache.org/jira/browse/DERBY-7162 > Project: Derby > Issue Type: Task > Components: Build tools > Reporter: Bob Neugebauer > Priority: Major > > There is an existing GIT mirror for DB-DERBY available at > [https://github.com/apache/derby] however this mirror is out of date. Last > commit was Aug 2019. This mirror is missing all branches and tags that the > derby SVN repo contains. > I had opened an INFRA ticket INFRA-25623 to request an update to git but > Chris said this had to come from the derby maintainers. > I have a project that is using derby, in particular 10.17, and I am looking > for the best way to avoid having our build servers hit ASF frequently to pull > from SVN. Using a git fork would seem the best way to achieve this. > > Thanks, Bob -- This message was sent by Atlassian Jira (v8.20.10#820010)