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

git svn problem

From
LGLuis Gutierrez <luis.gutierrez@arm.com>
Date
Jul 15, 2010, 11:00 UTC
Message-ID
<DBB61D38F7942B49AD43397D38954724080AB1@ZIPPY.Emea.Arm.com>
Hi,

I did the usual google search, wiki and mail list search looking for an answer, but I can't find it anywhere.

I'm trying to use git svn to interact with (surprise) and SVN repository. git svn clone <url> does the trick in getting a copy of the repo. However, there are a couple of misbehaving sym links that git-index does not know how to handle.

Doing a git-svn-rebase or a git-stash will result in this error:
> git stash

Saved working directory and index state WIP on master: 919e091 L2C: added X-checking assertions and l2c->RAM interface properties. error: git checkout-index: unable to create symlink < path to file> (File name too long) error: git checkout-index: unable to create symlink < path to file > <filename> (File name too long) fatal: Could not reset index file to revision 'HEAD'.

As far as I can tell, the symlink was full-path symlink (instead of the usual relative path) done by someone thousand of svn commits ago.

I've tried with both a full history import, and a shallow (the last 10 commits) import and in both cases I'm stuck with this files.

Now, I can't really replace this file with the svn one because on a git-svn-dcommit it will try to replace it.

As you can imagine, this is killing all the fun. 

Any ideas on what to do? I would really love to use git instead of SVN for development, but I'll settle for using just to browse the history and changes.

Regards,
Luis Gutierrez
-- 
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.
Message 1 of 1 in “git svn problem”
  1. Luis GutierrezJul 15, 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.