From: Hadmut Danisch <hadmut@danisch.de>
To: "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 15:44:09 +0100 [thread overview]
Message-ID: <aU/wuT23Ybllu/1q@danisch.de> (raw)
In-Reply-To: <aU_lqe2Z47STv68O@kitsune.suse.cz>
On Sat, Dec 27, 2025 at 02:56:57PM +0100, Michal Suchánek wrote:
>
> When you want it to be readable you do not need any special permission
> bits.
>
> You can set the directories and files to be readable by group, and
> ensure the container user is part of the group.
And that's the problem:
"ensure the container user is part of the group" is what the S_ISGID flag on directories is good for: It ensures that newly created directories inherit their parent's group. Unix administration basics.
And this is the bit git clears and breaks this mechanism.
regards
Hadmut
next prev parent reply other threads:[~2025-12-27 14:44 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
2025-12-27 14:44 ` Hadmut Danisch [this message]
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=aU/wuT23Ybllu/1q@danisch.de \
--to=hadmut@danisch.de \
--cc=git@vger.kernel.org \
--cc=msuchanek@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox