threads / discuss / 39633

Fwd: git svn die signal 6

Subject: Fwd: git svn die signal 6

## tl;dr

2 messages between Jun 15, 2015 and Jun 19, 2015.

replies: 1people: 1as markdown or json

Олег Кохтенко· Jun 15, 2015, 13:54 UTC · lore

Hi great "git crew" member :) I found small, but annoying bug in 'git svn'. If you would try to make any commit with new files (or delete/modify files) which contain in name "@" sign - you'll see crash with minimum information about what's just happened. Such file names are very useful for iOS projects when you can add same pictures with different dimensions with suffix @2x or @3x. In guts, svn uses "@" sign for pin version of file and it's probably confused if this sign presented in file name. For committing such changes thru svn you would use "svn add 'image@3x.png'@". This will prevent such problem.

I hope you can easily find out how to reproduce and fix this issue. Please, feel free to contact me for any details about this.

Best regards
Олег Кохтенко· Jun 19, 2015, 08:42 UTC · re: Олег Кохтенко · lore

Re: git svn die signal 6

I even found Pull Request on GitHub with useful changes, but looks like there is too hard way to commit changes and author gave up. https://github.com/git/git/pull/62 Probably you can take a short look into it and include this changes in next release.

2015-06-15 16:54 GMT+03:00 Олег Кохтенко <kohtenko@gmail.com>:
Show 15 quoted lines
> Hi great "git crew" member :)
> I found small, but annoying bug in 'git svn'. If you would try to make
> any commit with new files (or delete/modify files) which contain in
> name "@" sign - you'll see crash with minimum information about what's
> just happened. Such file names are very useful for iOS projects when
> you can add same pictures with different dimensions with suffix @2x or
> @3x. In guts, svn uses "@" sign for pin version of file and it's
> probably confused if this sign presented in file name. For committing
> such changes thru svn you would use "svn add 'image@3x.png'@". This
> will prevent such problem.
>
> I hope you can easily find out how to reproduce and fix this issue.
> Please, feel free to contact me for any details about this.
>
> Best regards

← back to recent threads