# Preserving ownership and set*id bits

2 messages from 2007-01-18 to 2007-01-18. Participants: Ron Parker, Andy Parkins.
Thread: https://gitlist.dev/t/6428

## Ron Parker, 2007-01-18 17:09

Subject: Preserving ownership and set*id bits
Message-ID: <769697AE3E25EF4FBC0763CD91AB1B0201D49679@MBGMail01.mobot.org>
URL: https://gitlist.dev/e/769697AE3E25EF4FBC0763CD91AB1B0201D49679%40MBGMail01.mobot.org

```
I am tracking a development web server in git.  The problem is that some
of the scripts I am tracing are setgid.  And certain files must have
different ownership.

I assumed that git would preserve the setgid bit as well as the user and
group of the files.  Since it is described as the "stupid directory
content manager" that just tracks the content of directories, I expected
it would maintain at least as much information as tar.  Oops.  Color me
stupid.

Anyway, I'm not here to complain, but I am looking for suggestions of
how I might store and preserve this information as well.  

I got bit when I did something equivalent to "git reset --hard HEAD^",
to back out a change.  I need someway of preserving this information
across commits, clones, pushes, pulls, etc.

Our development has been centered around the idea of using git to track
the changes to our development server and later "git pull" those changes
to the production server with GIT_DIR pointing to an out-of-directory
clone.

```

## Andy Parkins, 2007-01-18 20:10

Subject: Re: Preserving ownership and set*id bits
Message-ID: <200701182010.41183.andyparkins@gmail.com>
URL: https://gitlist.dev/e/200701182010.41183.andyparkins%40gmail.com
In-Reply-To: <769697AE3E25EF4FBC0763CD91AB1B0201D49679@MBGMail01.mobot.org>

```
On Thursday 2007, January 18 17:09, Ron Parker wrote:

> Anyway, I'm not here to complain, but I am looking for suggestions of
> how I might store and preserve this information as well.

Storing it is fairly easy.  You can use getfacl in the pre-commit hook to 
record all the file information you want.

The hard part (at the moment) is that there is no post-checkout hook that you 
could use to restore those attributes.

If you were willing to manually run that restoration script after every 
checkout then there is your answer.


Andy

-- 
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com

```