threads / discuss / 32699

git-svn problems with white-space in tag names

Subject: git-svn problems with white-space in tag names

## tl;dr

3 messages between Jan 23, 2013 and Feb 6, 2013.

replies: 2people: 2as markdown or json

Hans-Juergen Euler· Jan 23, 2013, 10:23 UTC · lore

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.

Hans-Juergen Euler· Jan 27, 2013, 14:12 UTC · re: Hans-Juergen Euler · lore

Re: git-svn problems with white-space in tag names

This seems to be a problem of the windows version. At least with its complete severity. Installed git on Ubuntu in a virtual machine was able to clone the subversion repos past the tag with the white-space at the end. I am not sure but apparently this tag has not been converted.

The git repos I could copy from Ubuntu to windows. So far no problems seen in this copy on windows.

2013/1/23 Hans-Juergen Euler <waas.nett@gmail.com>:

Show 39 quoted lines

> 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.

Erik Faye-Lund· Feb 6, 2013, 09:26 UTC · re: Hans-Juergen Euler · lore

Re: git-svn problems with white-space in tag names

On Sun, Jan 27, 2013 at 3:12 PM, Hans-Juergen Euler <waas.nett@gmail.com> wrote:

Show 9 quoted lines

> This seems to be a problem of the windows version. At least with its
> complete severity. Installed git on Ubuntu in a virtual machine was
> able to clone the subversion repos past the tag with the white-space
> at the end. I am not sure but apparently this tag has not been
> converted.
>
> The git repos I could copy from Ubuntu to windows. So far no problems
> seen in this copy on windows.
>

The cause of the problem is that the tagname isn't a valid filename on Windows, which git requires it to be.