Now, when you mount this disk image you can move all your git repos over to this Volume to enjoy a git that doesn't get confused by those pesky case-changes! Ensure "sparse bundle disk image" is set in "Image Format". Select "Single Partition - Apple Partition Map" in "Partitions".Select "Mac OS Extended (Case-sensitive, Journaled)" in "Format".Set the size to something that will most likely fit your needs (resizing is a whole another story).Enter a nice Name for your Volume, e.g "Workspace".So, a new approach to the solution!Įnter the world of read-write disk image using Disk Utility and use this newly created volume as your base working directory for working with git-repos! If all OS X users in your oragnization/company uses this approach, you should be good! Also, other people in your team will not get the filename changes you just comitted on a git pull. I did not find a good way to fix this problem. However this approach caused me major headaches when I was doing a pull-request and had to squash my commits before pushing it (and one commit included the case changes to filenames). Gives no guarantee that it won't f*ck up any other users checkout which most likely need to remove the file or checkout a clean copy of the git repo. Git commit -m "Set correct case for filename" The issue occurs when you use the default OS X disk format (case-preserving, but not case-sensitive) and try to rename a file or folder in git by changing letters to uppercase/lowercase.Ī typical hack around the issue is to execute multiple commands: git mv filename filename_tmp Found an awesome GIT tip for OSX users which are having problems with case-sensitivity and renaming of files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |