{"thread":{"id":"6428","subject":"Preserving ownership and set*id bits","startedAt":"2007-01-18T17:09:33Z","lastAt":"2007-01-18T20:10:39Z","messageCount":2,"participants":["Ron Parker","Andy Parkins"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"32006","messageId":"769697AE3E25EF4FBC0763CD91AB1B0201D49679@MBGMail01.mobot.org","threadId":"6428","inReplyTo":null,"subject":"Preserving ownership and set*id bits","fromName":"Ron Parker","fromEmail":"ron.parker@mobot.org","sentAt":"2007-01-18T17:09:33Z","receivedAt":"2007-01-18T17:09:33Z","isPatch":false,"sender":{"key":"ron.parker@mobot.org","avatar":null},"body":"I am tracking a development web server in git.  The problem is that some\nof the scripts I am tracing are setgid.  And certain files must have\ndifferent ownership.\n\nI assumed that git would preserve the setgid bit as well as the user and\ngroup of the files.  Since it is described as the \"stupid directory\ncontent manager\" that just tracks the content of directories, I expected\nit would maintain at least as much information as tar.  Oops.  Color me\nstupid.\n\nAnyway, I'm not here to complain, but I am looking for suggestions of\nhow I might store and preserve this information as well.  \n\nI got bit when I did something equivalent to \"git reset --hard HEAD^\",\nto back out a change.  I need someway of preserving this information\nacross commits, clones, pushes, pulls, etc.\n\nOur development has been centered around the idea of using git to track\nthe changes to our development server and later \"git pull\" those changes\nto the production server with GIT_DIR pointing to an out-of-directory\nclone.\n"},{"id":"32019","messageId":"200701182010.41183.andyparkins@gmail.com","threadId":"6428","inReplyTo":"769697AE3E25EF4FBC0763CD91AB1B0201D49679@MBGMail01.mobot.org","subject":"Re: Preserving ownership and set*id bits","fromName":"Andy Parkins","fromEmail":"andyparkins@gmail.com","sentAt":"2007-01-18T20:10:39Z","receivedAt":"2007-01-18T20:10:39Z","isPatch":false,"sender":{"key":"andyparkins@gmail.com","avatar":null},"body":"On Thursday 2007, January 18 17:09, Ron Parker wrote:\n\n> Anyway, I'm not here to complain, but I am looking for suggestions of\n> how I might store and preserve this information as well.\n\nStoring it is fairly easy.  You can use getfacl in the pre-commit hook to \nrecord all the file information you want.\n\nThe hard part (at the moment) is that there is no post-checkout hook that you \ncould use to restore those attributes.\n\nIf you were willing to manually run that restoration script after every \ncheckout then there is your answer.\n\n\nAndy\n\n-- \nDr Andrew Parkins, M Eng (Hons), AMIEE\nandyparkins@gmail.com\n"}]}