git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Preserving ownership and set*id bits

From
RPRon Parker <ron.parker@mobot.org>
Date
Jan 18, 2007, 17:09 UTC
Message-ID
<769697AE3E25EF4FBC0763CD91AB1B0201D49679@MBGMail01.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.

Next: Andy Parkins
Message 1 of 2 in “Preserving ownership and set*id bits”
  1. Ron ParkerJan 18, 2007
  2. Andy ParkinsJan 18, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.