From: jamespetts <jamespetts@yahoo.com>
To: 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 15:18:14 -0700 (PDT) [thread overview]
Message-ID: <1238278694146-2550633.post@n2.nabble.com> (raw)
In-Reply-To: <8c9a060903281504qd1b66hefb70e60c3f624d2@mail.gmail.com>
Thank you for replying again so soon :-)
I tried using the exact command that you gave me earlier, but got the identical error:
git: 'svn' is not a git-command. See 'git --help'.
On Sat, Mar 28, 2009 at 14:46, jamespetts <jamespetts@yahoo.com> wrote:
>
> Thank you for your reply. Unfortunately, I cannot for the life of me get git-svn to work. It refuses to recognise "git svn" as a valid command, and "svn" does not appear in the list of commands when I type, "svn --help" in Git Bash (I am using Git in Windows, if that makes any difference). I tried to look for svn2git, but the homepage linked from the link that you gave me produced a 404.
>
> Also, once I have managed to create a Git clone of the SVN repository myself, how do I synchronise that properly with the branch of the other mirror of the SVN repository that I have been using as the trunk so far, such that I can continue to download updates and have [i]just[/i] the changes since the previous versions applied?
>
>
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
> --
> View this message in context: http://n2.nabble.com/Fork-of-abandoned-SVN-mirror---how-to-keep-up-to-date-with-the-SVN-tp2548952p2550565.html
> Sent from the git mailing list archive at Nabble.com.
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
You should be able to use the exact command I showed earlier within
"git bash". Also, you'd want to type "git help svn", not "svn --help"
to see the manual.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
View this message in context: http://n2.nabble.com/Fork-of-abandoned-SVN-mirror---how-to-keep-up-to-date-with-the-SVN-tp2548952p2550633.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2009-03-28 22:19 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
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 [this message]
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=1238278694146-2550633.post@n2.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.