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: Sun, 29 Mar 2009 08:07:10 -0700 (PDT) [thread overview]
Message-ID: <1238339230806-2552797.post@n2.nabble.com> (raw)
In-Reply-To: <fabb9a1e0903290555o3503b58ie097f8f8336c4401@mail.gmail.com>
Heya,
On Sun, Mar 29, 2009 at 14:53, jamespetts <jamespetts@yahoo.com> wrote:
>
> "Unable to determine upstream SVN infromation from working tree history".
>
> Have I done something wrong...?
I'm afraid this is where my git-svn knowledge is no longer sufficient
:(. I have had the same problem myself, and I don't know how to fix
it, perhaps Eric has a moment to enlighten?
Supposing that Eric is unable to find a solution - would there be any mileage in doing it manually? That is, checking out the SVN repository into a local directory, initialising that as a Git repository, and then pushing it to Github? If so, would that make it any harder to re-synchronise with my branch than the git-svn method?
--
View this message in context: http://n2.nabble.com/Fork-of-abandoned-SVN-mirror---how-to-keep-up-to-date-with-the-SVN-tp2548952p2552797.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2009-03-29 15:08 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
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 [this message]
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=1238339230806-2552797.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 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).