{"thread":{"id":"3720","subject":"Perserving permissions?","startedAt":"2006-03-25T10:48:11Z","lastAt":"2006-03-25T10:48:11Z","messageCount":1,"participants":["Jeff Garzik"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"17930","messageId":"44251FEB.70008@garzik.org","threadId":"3720","inReplyTo":null,"subject":"Perserving permissions?","fromName":"Jeff Garzik","fromEmail":"jeff@garzik.org","sentAt":"2006-03-25T10:48:11Z","receivedAt":"2006-03-25T10:48:11Z","isPatch":false,"sender":{"key":"jeff@garzik.org","avatar":null},"body":"\nI just started using git to maintain some of my server config files. \nLeagues better than subversion, which I was previously using, but git \nstill suffers from a key problem that subversion also has:  lack of \npermission preservation.\n\nI understand that versioning permissions might be a big request, but \nwhat about simply storing the permissions at 'git add' time, to be used \nat checkout time?\n\nRight now I have to do 'git pull ; ./fix-perms' each time I update.\n\n\tJeff\n"}]}