If use uppercase file extension, svn:eol-style will fail

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Create svn repo with standard folder structure.

2. Do git svn clone via TortoiseGit.

3. Modify ~\.subversion\config
    (C:\Documents and Settings\{UserName}\.subversion\config)
    [miscellany]
      enable-auto-props = yes
    [auto-props]
      *.dsp = svn:eol-style=CRLF
      *.dsw = svn:eol-style=CRLF
    (this config file is created by git or tgit?)

4. Do git add and git commit on test.DSW via TortoiseGit.
    ※ Note1: the file extension is uppercase and eol is CRLF
    ※ Note2: AutoCrlf checkbox is checded and SafeCrLf is false in settings Dialog

5. Do git svn dcommit via TortoiseGit.

6. Do svn checkout trunk and eol of test.DSW is LF.

What is the expected output? What do you see instead?

Eol should be CRLF.

What version of TortoiseGit and msysgit are you using? On
what operating system?

TortoiseGit 1.8.5.0
git version 1.8.3.msysgit.0
XPP SP3

Please provide any additional information below.

I also tested 2 situations:

This first one:

Copy test.DSW to test1.dsw in git version control folder
(※ Note: new file extension is lowercase)

Do git add and git commit on test1.dsw

Do git svn dcommit via TortoiseGit

Do svn update in working copy folder.

Eol of Test1.dsw which in the svn working copy folder is CRLF. (It’s ok.)

The other one:

Modify %appdata%\Subversion\config
(C:\Documents and Settings\{UserName}\Application Data\Subversion\config)
[miscellany]
  enable-auto-props = yes
[auto-props]
  *.dsp = svn:eol-style=CRLF
  *.dsw = svn:eol-style=CRLF

Copy test.DSW(LF) to test2.DSW(LF) in svn working cpoy folder

Do svn commit on test2.DSW, and eol of test2.DSW changed from LF to CRLF. 
(It’s ok.)

Original issue reported on code.google.com by yuelinho...@gmail.com on 26 Sep 2013 at 6:00

[GoogleCodeExporter]

I use Git Bash test the case and the result is still failed.
The eol of the file with uppercase file extension is still LF in svn working 
copy.

Original comment by yuelinho...@gmail.com on 30 Sep 2013 at 1:14

[GoogleCodeExporter]

Should I post the issue to msysgit?
If Yes, Could you tell me how to do that?
Post issue on https://github.com/msysgit/msysgit/issues?
or Mail to msysgit@googlegroups.com?
or something else?

Thank you! ^_^

Original comment by yuelinho...@gmail.com on 30 Sep 2013 at 1:54

[GoogleCodeExporter]

I think you'd better start discussing in thew group, and maybe even core git 
group, not msysgit or cygwin-git Windows ports.

http://dir.gmane.org/search.php?match=git

Part of the issue is that GIT started as a Linux application, so for Git files 
like "aaa.txt" "aaa.TXT" and "aaa.tXt" are three different unrelated files, 
just like vaiables in C++.

If SVN ignores difference in such filenames, then either it is incompatible 
with Linux/BSD/MacOS/etc or it has two very distinct modes for Windows and for 
rest of the world.

Original comment by Arioch...@gmail.com on 10 Oct 2013 at 7:18

[GoogleCodeExporter]

Thank you so much! ^_^

Original comment by yuelinho...@gmail.com on 11 Oct 2013 at 6:56

[GoogleCodeExporter]

Original comment by sstrickr...@googlemail.com on 20 Oct 2013 at 2:21

• Changed state: ThirdPart