git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jamespetts <jamespetts@yahoo.com>
To: git@vger.kernel.org
Subject: Fork of abandoned SVN mirror - how to keep up to date with the SVN
Date: Sat, 28 Mar 2009 06:11:33 -0700 (PDT)	[thread overview]
Message-ID: <22756729.post@talk.nabble.com> (raw)


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.

             reply	other threads:[~2009-03-28 13:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28 13:11 jamespetts [this message]
2009-03-28 16:22 ` Fork of abandoned SVN mirror - how to keep up to date with the SVN Jacob Helwig
2009-03-28 16:46   ` jamespetts
2009-03-28 18:02     ` Jacob Helwig
2009-03-28 18:06       ` jamespetts
2009-03-28 20:27         ` Jacob Helwig
2009-03-28 21:46           ` jamespetts
2009-03-28 21:55             ` Sverre Rabbelier
2009-03-28 22:01               ` jamespetts
2009-03-28 22:04             ` Jacob Helwig
2009-03-28 22:18               ` jamespetts
2009-03-28 22:21                 ` Sverre Rabbelier
2009-03-29 10:51                   ` jamespetts
2009-03-29 11:03                     ` Sverre Rabbelier
2009-03-29 11:52                       ` jamespetts
2009-03-29 12:03                         ` Sverre Rabbelier
2009-03-29 12:08                           ` jamespetts
2009-03-29 12:35                             ` Sverre Rabbelier
2009-03-29 12:53                               ` jamespetts
2009-03-29 12:55                                 ` Sverre Rabbelier
2009-03-29 15:07                                   ` jamespetts
2009-03-29 22:16                                   ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22756729.post@talk.nabble.com \
    --to=jamespetts@yahoo.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).