| |||||||||||||
A proposed Subversion vision and roadmapA proposed Subversion vision and roadmapPosted Apr 5, 2010 16:36 UTC (Mon) by cortana (subscriber, #24596)In reply to: A proposed Subversion vision and roadmap by shmget Parent article: A proposed Subversion vision and roadmap
Please, no more snide remarks.
Many of us use Windows for our day job, and work on a variety of projects with different version
I don't think anyone could honestly state that the Windows port of git is as polished as its
(Log in to post comments)
A proposed Subversion vision and roadmap Posted Apr 6, 2010 16:48 UTC (Tue) by Spudd86 (guest, #51683) [Link]
The main issue I've had using git on windows has been line endings and filename case, both confuse git into thinking a file in my working copy is different from the HEAD when in fact it is not, and trying to do a commit confuses git. (Filename case confuses it during checkout, if the file has the name "Foo.c" in the working copy for some strange reason, while git thinks of it as being foo.c it will be confused... I'm not actually sure how I got into that situation...)
The line ending issue is avoidable by just turning off line ending conversion entirely and using a text editor other than Notepad.
The second is a result of Windows breaking an assumption git makes about file names, and really Windows' case insensitive file names are a pain to deal with in a portable way... you pretty much have to write a crapload of code twice...
A proposed Subversion vision and roadmap Posted Apr 6, 2010 20:25 UTC (Tue) by vonbrand (subscriber, #4458) [Link] What you describe is the mess caused by Windows and Unix using different line ending conventions. It bites you everywhere...
A proposed Subversion vision and roadmap Posted Apr 6, 2010 23:07 UTC (Tue) by dlang (✭ supporter ✭, #313) [Link]
git supports work-arounds for both of these problems
you can tell git to change the line ending when a file is checked in, checked out, both, or neither. you can modify this by editing the git config file or useing the git config command.
you can tell git what to do about case sensitivity (although I don't remember the details of how to set this.
A proposed Subversion vision and roadmap Posted Apr 8, 2010 16:30 UTC (Thu) by Spudd86 (guest, #51683) [Link]
I'm aware that I can tell git to do line ending conversion, however the case sensitivity thing was basically git thought it had a file Foo.txt that was untracked and a file foo.txt that was, then when I try to do some things git refuses to do it because it thinks it's about to blow away something... (ie checkout a new file on top of an untracked one)
A proposed Subversion vision and roadmap Posted Apr 8, 2010 18:19 UTC (Thu) by dlang (✭ supporter ✭, #313) [Link]
I believe that you can set case sensitivity as well. There has definitely been a lot of discussion on the subject and how to deal with it. I just don't remember how to configure it.
|
|||||||||||||