{"thread":{"id":"26562","subject":"x permission lost on Windows merge","startedAt":"2011-02-19T20:29:37Z","lastAt":"2011-02-19T20:29:37Z","messageCount":1,"participants":["Lyle"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"161716","messageId":"4D602831.8060200@cosmicperl.com","threadId":"26562","inReplyTo":null,"subject":"x permission lost on Windows merge","fromName":"Lyle","fromEmail":"webmaster@cosmicperl.com","sentAt":"2011-02-19T20:29:37Z","receivedAt":"2011-02-19T20:29:37Z","isPatch":false,"sender":{"key":"webmaster@cosmicperl.com","avatar":null},"body":"Hi All,\n   I was just on IRC chatting about this issue. What I'm finding is that \nif a merge happens on a Windows git repo the x permission is lost, \nexample (filename changed):\n\nfilename.pl\n\n----------------------------- filename.pl -----------------------------\nindex 0388de4,94d7e76..9c31830\nmode 100755,100755..100644\n\nAs you can see, both of the modified files are 0755 but the merged file \nis 0644. I know windows files don't have the x permission, which \nexplains why the newly created merged file would be missing the x, but \nsurely with filemode = false the behaviour should be to carry over the x \nfrom the two modified files?\n\nThis is causing me problems when the merged file gets pulled back onto \nLinux systems where it needs the x permission.\n\n\nLyle\n"}]}