{"thread":{"id":"28373","subject":"windows git problem","startedAt":"2011-09-12T17:35:10Z","lastAt":"2011-09-13T10:30:51Z","messageCount":5,"participants":["luis","Michael Witten","Nguyen Thai Ngoc Duy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"175348","messageId":"4E6E42CE.80405@tandvsolns.co.uk","threadId":"28373","inReplyTo":null,"subject":"windows git problem","fromName":"luis","fromEmail":"luis@tandvsolns.co.uk","sentAt":"2011-09-12T17:35:10Z","receivedAt":"2011-09-12T17:35:10Z","isPatch":false,"sender":{"key":"luis@tandvsolns.co.uk","avatar":null},"body":"Hi Guys,\n\nI recently run into a funny git situation.\n\nI had a directory under git control named \"someName\", with a bunch of \nfiles inside. This was committed and working for some time.\nI then added a file name \"somename\", and under linux, that worked OK.\nHowever when I checked out the project under windows (either clone or \npull) one or the other would disappear and it would be staged as removed.\n\nThe surprising bit for me was not so much that windows could not cope \nwith the case sensitivity, but that git would stage the changes!\n\nI have attached a new git project with the problem that should help show \nthe issue.\nIf you clone from this repo on a windows box you should be able to see it\n\nBTW, I'm using git v 1.7.4.1\n\n-- \nLuis Gutierrez\nTest and Verification Solutions (TVS)\nskype: luis.tandv\n\n"},{"id":"175349","messageId":"CAMOZ1Bs6tGGJ8eZja0OaqtzK0imKt_NtiWOTgpLCaisvEXh2Rw@mail.gmail.com","threadId":"28373","inReplyTo":"4E6E42CE.80405@tandvsolns.co.uk","subject":"Re: windows git problem","fromName":"Michael Witten","fromEmail":"mfwitten@gmail.com","sentAt":"2011-09-12T18:05:32Z","receivedAt":"2011-09-12T18:05:32Z","isPatch":false,"sender":{"key":"mfwitten@gmail.com","avatar":"https://avatars.githubusercontent.com/u/597101?v=4"},"body":"On Mon, Sep 12, 2011 at 17:35, luis wrote:\n> However when I checked out the project under windows (either clone or pull)\n> one or the other would disappear and it would be staged as removed.\n>\n> The surprising bit for me was not so much that windows could not cope with\n> the case sensitivity, but that git would stage the changes!\n\nIt would be recorded in the index as a change ready to be committed\n(as though `git rm' had been used)?\n"},{"id":"175352","messageId":"4E6E5000.3040203@tandvsolns.co.uk","threadId":"28373","inReplyTo":"CAMOZ1Bs6tGGJ8eZja0OaqtzK0imKt_NtiWOTgpLCaisvEXh2Rw@mail.gmail.com","subject":"Re: windows git problem","fromName":"luis","fromEmail":"luis@tandvsolns.co.uk","sentAt":"2011-09-12T18:31:28Z","receivedAt":"2011-09-12T18:31:28Z","isPatch":false,"sender":{"key":"luis@tandvsolns.co.uk","avatar":null},"body":"Exactly!\n\nso the next time someone (in windows) does a commit, they remove the \nfile or the folder contents!\n\nOn 12/09/11 19:05, Michael Witten wrote:\n> On Mon, Sep 12, 2011 at 17:35, luis wrote:\n>> However when I checked out the project under windows (either clone or pull)\n>> one or the other would disappear and it would be staged as removed.\n>>\n>> The surprising bit for me was not so much that windows could not cope with\n>> the case sensitivity, but that git would stage the changes!\n> It would be recorded in the index as a change ready to be committed\n> (as though `git rm' had been used)?\n>\n\n-- \nLuis Gutierrez\nTest and Verification Solutions (TVS)\nskype: luis.tandv\n"},{"id":"175396","messageId":"CACsJy8B4RY4Yst9TPhNCOj8AUziFa+O+2Msen9Bt=QHo5SW=sA@mail.gmail.com","threadId":"28373","inReplyTo":"4E6E5000.3040203@tandvsolns.co.uk","subject":"Re: windows git problem","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2011-09-13T10:10:40Z","receivedAt":"2011-09-13T10:10:40Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Tue, Sep 13, 2011 at 4:31 AM, luis wrote:\n> Exactly!\n>\n> so the next time someone (in windows) does a commit, they remove the file or\n> the folder contents!\n\nMay be this commit dc1ae70 (Support case folding for git add when\ncore.ignorecase=true). Forcing core.ignorecase to add_to_index() seems\na bit too strong for me. We could have added a new flag,\nADD_CASE_INSENSITIVE, to add_to_index() and enabled it only to\nselected commands instead.\n\nOr maybe we can improve the situation a little bit by warning users this case.\n-- \nDuy\n"},{"id":"175397","messageId":"CACsJy8Cy0nFuAVzfN9sGgd3wiQ1HE2ASW7vqY5PGt4bH4BCvtg@mail.gmail.com","threadId":"28373","inReplyTo":"CACsJy8B4RY4Yst9TPhNCOj8AUziFa+O+2Msen9Bt=QHo5SW=sA@mail.gmail.com","subject":"Re: windows git problem","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2011-09-13T10:30:51Z","receivedAt":"2011-09-13T10:30:51Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Tue, Sep 13, 2011 at 8:10 PM, Nguyen Thai Ngoc Duy wrote:\n> On Tue, Sep 13, 2011 at 4:31 AM, luis wrote:\n>> Exactly!\n>>\n>> so the next time someone (in windows) does a commit, they remove the file or\n>> the folder contents!\n>\n> May be this commit dc1ae70 (Support case folding for git add when\n> core.ignorecase=true).\n\nI take it back. add_to_index() is mostly called by git-add. A checkout\nfills the index with unpack-trees, which does not seem to be\ncase-insensitive to me.\n-- \nDuy\n"}]}