[
https://issues.apache.org/jira/browse/SOLR-8653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139978#comment-15139978
]
Jan Høydahl commented on SOLR-8653:
-----------------------------------
I tried to rebase an old GitHub fork to the new repo, using these commands
{code}
git remote add upstream https://github.com/apache/lucene-solr.git
git fetch upstream
git checkout trunk
git rebase upstream/master
{code}
However, it failed so I give up trying to write instructions on how to just
switch your current clone to get up to date with new master.
I wrote a small chapter in the wiki about what we advise people to do:
https://wiki.apache.org/solr/HowToContribute#Working_with_GitHub and linked to
it from the revised news story at
http://lucene.staging.apache.org/solr/news.html. Comments welcome both on the
wiki paragraph and the revised staged news page.
> Apache Solr page still directs people to Subversion
> ---------------------------------------------------
>
> Key: SOLR-8653
> URL: https://issues.apache.org/jira/browse/SOLR-8653
> Project: Solr
> Issue Type: Bug
> Reporter: Erick Erickson
>
> This page needs to be updated desperately:
> http://lucene.apache.org/solr/resources.html#solr-version-control as it's all
> about Subversion
> Arguably a bug, but I wouldn't object to it being changed to "improvement"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
