From: Gabor Gombas <gombasgg@gmail•com>
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 22:49:55 +0100 [thread overview]
Message-ID: <aVBUg289AKC0HIVx@lan> (raw)
In-Reply-To: <74793560-49ae-494e-afff-9b833dd25d1c@danisch.de>
On Sat, Dec 27, 2025 at 03:40:11PM +0100, Hadmut Danisch wrote:
> 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.
Well, default ACLs may very well be the solution to your problem,
because git does not understand ACLs, so it would leave them alone. Of
coure, managing ACLs at scale have their fair share of problems, so
YMMV. The problem with the permission bits is git trying to be clever
and thinking it can manage them - but as often, trying to be clever ends
up not being clever at all. Unfortunately, there does not seem to be a
configuration option to tell git to leave permission bits alone.
core.filemode is the closest one, but what you want is the opposite
behavior - what you want is not ignoring the executable bit, but
ignoring everything _except_ the executable bit. Maybe you can try to
make a patch...
Regards,
Gabor
next prev parent reply other threads:[~2025-12-27 21:49 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
2025-12-27 21:49 ` Gabor Gombas [this message]
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=aVBUg289AKC0HIVx@lan \
--to=gombasgg@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=hadmut@danisch$(echo .)de \
--cc=msuchanek@suse$(echo .)de \
--cc=rsbecker@nexbridge$(echo .)com \
/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