From: Jacob Helwig <jacob.helwig@gmail.com>
To: jamespetts <jamespetts@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: Fork of abandoned SVN mirror - how to keep up to date with the SVN
Date: Sat, 28 Mar 2009 13:27:07 -0700 [thread overview]
Message-ID: <8c9a060903281327j33056807j78a2cd03b8151979@mail.gmail.com> (raw)
In-Reply-To: <1238263580197-2549943.post@n2.nabble.com>
On Sat, Mar 28, 2009 at 11:06, jamespetts <jamespetts@yahoo.com> wrote:
>
> Thank you very much for your reply :-) Ahh, I didn't realise that that sort of SVN URL should be avoided. Is there any way around that when the project itself uses that sort of URL? And I think that it does require a username and empty password. I haven't tried the Github IRC channel - I must confess - I did not know that there was one.
>
> Any suggestions about how to deal with the other problem?
>
It looks like GitHub won't keep the project in sync for you, so you're
probably best off doing the git-svn clone yourself, and maintaining it
that way.
http://github.com/guides/import-from-subversion
next prev parent reply other threads:[~2009-03-28 20:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 13:11 Fork of abandoned SVN mirror - how to keep up to date with the SVN jamespetts
2009-03-28 16:22 ` 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 [this message]
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=8c9a060903281327j33056807j78a2cd03b8151979@mail.gmail.com \
--to=jacob.helwig@gmail.com \
--cc=git@vger.kernel.org \
--cc=jamespetts@yahoo.com \
/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).