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

git-svn problems with white-space in tag names

From
HEHans-Juergen Euler <waas.nett@gmail.com>
Date
Jan 23, 2013, 10:23 UTC
Message-ID
<CAK3CF+4GPKBfAmgsHYnf_6nCCOCe-1d31cGsWp4jkKC28cZr0g@mail.gmail.com>

I have discussed already the problem a bit more in this thread groups.google.com/d/topic/git-users/kfMFZ3uEFsM/discussion

-----Operating system (specifically which version) windows 7 64 bit

------Git version (git --version) Git version 1.8.0 for windows obviously. git bash and git gui installed and using

------Git configuration (system, home, repository) hmm guess is covered with git bash and git gui. Using the standard config stuff

using subversion TortoiseSVN 1.7.11 Subversion 1.7.8 Was typically always up-to-date (within 2 months or so) with previous versions

using an external subversion provider for storing the information externally. guess the version there is older but do not know

I have tried to convert some of my external subversion data bases with git-svn clone

I have encountered a problem with one of my subversion repos. I have obviously introduced about 2 years ago a problem with an additional white space at the end of tag name.

So there is an entry "tags/blabla "

in the subversion repos. The sequential handling of the svn repos with git-svn gets stuck there. I could not find a way around this. My guess is that the white-space was introduced by accident on windows by Tortoise-SVN. Unfortunately this occurs at revision 90 something and I have almost 1000 revisions stored.

Let me know if you need more details.Thanks.
Next: Hans-Juergen Euler
Message 1 of 3 in “git-svn problems with white-space in tag names”
  1. Hans-Juergen EulerJan 23, 2013
  2. Hans-Juergen EulerJan 27, 2013
  3. Erik Faye-LundFeb 6, 2013

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.