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

Re: Import of svn rep has path issues

From
USUlrich Spörlein <uqs@spoerlein.net>
Date
May 2, 2010, 08:15 UTC
Message-ID
<20100502081510.GF92627@acme.spoerlein.net>
In-Reply-To
<8439yblorn.fsf@gmail.com>
On Sat, 01.05.2010 at 14:45:00 +0100, Paulo J. Matos wrote:
Show 19 quoted lines
> Hi all,
> 
> I just tried to import a svn project into git using git-svnimport.
> I followed:
> http://weblog.redlinesoftware.com/2008/2/24/converting-subversion-repositories-to-git
> 
> The line was:
> git-svnimport -C projname -r -v -A authors https://your-repo-host.com/projname
> 
> Interestingly some revisions resulted in a lot of errors with:
> 91: Unrecognized path: /main.cc
> 
> This seems to occur in the first revisions where I hadn't adopted a tree
> format of /branches, /tags, /trunk. 
> On the other hand, git-svnimport returned 0 to the environment, so I
> would assume that those 'Unrecognized path' issues are just warnings and
> everything went fine. I would like to have some confirmation of this if
> possible and if these files were not imported into my new git rep, how
> can I solve these issues?

Well, just look at your git-repo then and see if the logs indicate this file made it (I doubt it).

Please have a look at svn2git, which can take rules for what to do with specific paths at specific revisions. This should make it possible to go from

/ is master in git
to
/trunk is master in git
with little effort

Regards, Uli

Previous: Paulo J. MatosNext: Paulo J. Matos
Message 2 of 3 in “Import of svn rep has path issues”
  1. Paulo J. MatosMay 1, 2010
  2. Ulrich SpörleinMay 2, 2010
  3. Paulo J. MatosMay 4, 2010

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.