git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Fork of abandoned SVN mirror - how to keep up to date with the SVN

From
jamespetts <jamespetts@yahoo.com>
Date
Mar 28, 2009, 13:11 UTC
Message-ID
<22756729.post@talk.nabble.com>

For some months, I have been working on a http://github.com/jamespetts/simutrans-experimental/tree fork of the popular open source transport simulation game, http://www.simutrans.com Simutrans . Simutrans uses SVN as its official VCS, but I have been using Git, by forking an http://github.com/aburch/simutrans/tree/master unofficial mirror of the Simutrans SVN on Github. That has made it extremely easy for me to merge in updates to the trunk code whilst continuing to work on my branch.

However, last week, the unofficial mirror on Github suddenly stopped tracking the updates on the SVN. I have sent a message to the person who administers it, but he has not been around for a long time, and I fear that he probably will not reply - he did not reply to a message that I sent him some time ago. I do not really know what to do now to keep my branch synchronised. I have tried creating my own mirror of the SVN on Github, but there are two problems: (1) I cannot for the life of me get the creation of the mirror to work - it gets stuck permanently at "fetching authors"; and (2) even if I did succeed in creating a mirror, it would no longer be the same as the branch from which I forked, so Git would not be able to keep a track of which parts of the code I intend to keep different from the trunk, and which are the new updates to the trunk that I want to incorporate in my branch.

What is the best way of dealing with this mess to try to re-instate an easy and reliable system of taking updates from the SVN and merging them into my branched code?

-- 
View this message in context: http://www.nabble.com/Fork-of-abandoned-SVN-mirror---how-to-keep-up-to-date-with-the-SVN-tp22756729p22756729.html
Sent from the git mailing list archive at Nabble.com.
Next: Jacob Helwig
Message 1 of 22 in “Fork of abandoned SVN mirror - how to keep up to date with the SVN”
  1. jamespettsMar 28, 2009
  2. Jacob HelwigMar 28, 2009
  3. jamespettsMar 28, 2009
  4. Jacob HelwigMar 28, 2009
  5. jamespettsMar 28, 2009
  6. Jacob HelwigMar 28, 2009
  7. jamespettsMar 28, 2009
  8. Sverre RabbelierMar 28, 2009
  9. jamespettsMar 28, 2009
  10. Jacob HelwigMar 28, 2009
  11. jamespettsMar 28, 2009
  12. Sverre RabbelierMar 28, 2009
  13. jamespettsMar 29, 2009
  14. Sverre RabbelierMar 29, 2009
  15. jamespettsMar 29, 2009
  16. Sverre RabbelierMar 29, 2009
  17. jamespettsMar 29, 2009
  18. Sverre RabbelierMar 29, 2009
  19. jamespettsMar 29, 2009
  20. Sverre RabbelierMar 29, 2009
  21. jamespettsMar 29, 2009
  22. Eric WongMar 29, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.