From: Andreas Schwab <schwab@linux-m68k.org>
To: Hadmut Danisch <hadmut@danisch.de>
Cc: rsbecker@nexbridge.com, "'Michal Suchánek'" <msuchanek@suse.de>,
git@vger.kernel.org
Subject: Re: Git destroys u+s and g+s directory modes
Date: Sat, 27 Dec 2025 16:12:58 +0100 [thread overview]
Message-ID: <87ldiovtz9.fsf@igel.home> (raw)
In-Reply-To: <74793560-49ae-494e-afff-9b833dd25d1c@danisch.de> (Hadmut Danisch's message of "Sat, 27 Dec 2025 15:40:11 +0100")
On Dez 27 2025, 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.
You can set the default ACL on a directory, which is then inherited by
all newly created files.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2025-12-27 15:22 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 [this message]
2025-12-27 15:19 ` rsbecker
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=87ldiovtz9.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=hadmut@danisch.de \
--cc=msuchanek@suse.de \
--cc=rsbecker@nexbridge.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.