{"thread":{"id":"46","subject":"git-pasky file mode handling","startedAt":"2005-04-16T09:45:59Z","lastAt":"2005-04-16T14:56:50Z","messageCount":2,"participants":["Russell King","Petr Baudis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"290","messageId":"20050416104559.A12943@flint.arm.linux.org.uk","threadId":"46","inReplyTo":null,"subject":"git-pasky file mode handling","fromName":"Russell King","fromEmail":"rmk@arm.linux.org.uk","sentAt":"2005-04-16T09:45:59Z","receivedAt":"2005-04-16T09:45:59Z","isPatch":false,"sender":{"key":"rmk@arm.linux.org.uk","avatar":null},"body":"Hi,\n\nIt seems that there's something weird going on with the file mode\nhandling.  Firstly, some files in the git-pasky repository have mode\n0664 while others have 0644.\n\nHaving pulled from git-pasky a number of times, with Petr's being the\n\"tracked\" repository, I now find that when I do an update-cache --refresh,\nit complains that the files need updating, despite show-diff showing no\ndifferences.  Investigating, this appears to be because the file modes\nare wrong for a number of the files.  All my files do not have group\nwrite.\n\nI notice in the changelog what appears to be a dependence on the umask.\nIf this is so, please note that git appears to track the file modes,\nand any dependence upon the umask is likely to screw with this tracking.\n\n-- \nRussell King\n\n"},{"id":"309","messageId":"20050416145650.GB19099@pasky.ji.cz","threadId":"46","inReplyTo":"20050416104559.A12943@flint.arm.linux.org.uk","subject":"Re: git-pasky file mode handling","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-16T14:56:50Z","receivedAt":"2005-04-16T14:56:50Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Sat, Apr 16, 2005 at 11:45:59AM CEST, I got a letter\nwhere Russell King <rmk@arm.linux.org.uk> told me that...\n> Hi,\n\nHello,\n\n> It seems that there's something weird going on with the file mode\n> handling.  Firstly, some files in the git-pasky repository have mode\n> 0664 while others have 0644.\n> \n> Having pulled from git-pasky a number of times, with Petr's being the\n> \"tracked\" repository, I now find that when I do an update-cache --refresh,\n> it complains that the files need updating, despite show-diff showing no\n> differences.  Investigating, this appears to be because the file modes\n> are wrong for a number of the files.  All my files do not have group\n> write.\n\nthis is was a problem with git apply, which did not apply mode changes\ncorrectly until recently. If you have no local changes,\n\n\tcheckout-cache -f -a\n\nshould fix this. Hopefully.\n\n> I notice in the changelog what appears to be a dependence on the umask.\n> If this is so, please note that git appears to track the file modes,\n> and any dependence upon the umask is likely to screw with this tracking.\n\nI personally don't think I like the mode tracking at all. Some people\n(Linus?) may want to have group +w. Other people (me) have their default\ngroup as 'users', and I definitively don't want everyone to be able to\nwrite to the files. :-)\n\nI think we should track only whether the file is executable or not.\nLinus?\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"}]}