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

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

From
jamespetts <jamespetts@yahoo.com>
Date
Mar 29, 2009, 15:07 UTC
Message-ID
<1238339230806-2552797.post@n2.nabble.com>
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.
Previous: Sverre RabbelierNext: Eric Wong
Message 21 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.