public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge•com>
To: "'Hadmut Danisch'" <hadmut@danisch•de>,
	"'Michal Suchánek'" <msuchanek@suse•de>
Cc: <git@vger•kernel.org>
Subject: RE: Git destroys u+s and g+s directory modes
Date: Sat, 27 Dec 2025 10:19:44 -0500	[thread overview]
Message-ID: <009101dc7744$3ead0480$bc070d80$@nexbridge.com> (raw)
In-Reply-To: <74793560-49ae-494e-afff-9b833dd25d1c@danisch.de>

On December 27, 2025 9:40 AM, Hadmut Danisch wrote:
> Am 27.12.25 um 15:27 schrieb rsbecker@nexbridge•com:
> > There is an option with ubuntu: Access Control Lists (ACLs). These
> > provide override security for directories that might assist in your
> > process without having to worry about git security settings. It might
> > be worth looking into this option.
> 
> 
> This does not solve the problem, since ACLs do not propagate into newly created
> subdirectories, as group ownership with S_ISGID flag does.
> 
> 
> Please try to understand the problem before trying to solve it.

Without trying to be critical, the POSIX ACLs I have seen provide an option
that provides inheritance, so nothing in the repository will block those. That
is why I mentioned it. However, perhaps ubuntu does not support that
capability.


  parent reply	other threads:[~2025-12-27 15:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-27  2:37 Git destroys u+s and g+s directory modes Hadmut Danisch
2025-12-27 13:56 ` Michal Suchánek
2025-12-27 14:27   ` rsbecker
2025-12-27 14:40     ` Hadmut Danisch
2025-12-27 15:12       ` Andreas Schwab
2025-12-27 15:19       ` rsbecker [this message]
2025-12-27 21:49       ` Gabor Gombas
2025-12-27 14:44   ` Hadmut Danisch
2026-01-02  7:55 ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='009101dc7744$3ead0480$bc070d80$@nexbridge.com' \
    --to=rsbecker@nexbridge$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=hadmut@danisch$(echo .)de \
    --cc=msuchanek@suse$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox