From: David Chmelik <davidnchmelik@gmail.com>
To: git-l <git@vger.kernel.org>
Subject: Re: 'git clone,' build makes user non-writable files (should be option keep user-writable)
Date: Fri, 22 Jul 2022 17:25:35 -0700 [thread overview]
Message-ID: <ccbc1e81-b406-9e73-7aa5-956ffae7074b@gmail.com> (raw)
In-Reply-To: <CAPx1Gvc6ci1CjhL-zjwqkR=4o2yQTrT0V_Hb9bUBNuaBn47M8A@mail.gmail.com>
On 7/22/22 10:40 AM, Chris Torek wrote:
> On Fri, Jul 22, 2022 at 6:24 AM David Chmelik <dchmelik@gmail.com
> <mailto:dchmelik@gmail.com>> wrote:
>
> Ownership, permissions are different: one can own files yet have zero
> permission to write/delete and be denied that. ...
>
>
> All true. But Git has no control over, or affect on these: Git does
> not attempt to affect ownership or permission of any build products
> at all. Git only attempts to affect the execute permission of
> specific files as directed by the committed file mode (and provided
> `core.filemode` is enabled).
Not even projects' .git* subdirectories? They typically are/become
user-non-writable though deletable with several/many confirmations so I
usually sudo (recommended against). I'd rather opt-out of .git*
subdirectories for every clone.
> [...] If you're using Samba/CIFS or other ACL-based file servers [...]
I don't know what those are (other than once tried Samba to transfer
files between home PCs, not for compiling).
next prev parent reply other threads:[~2022-07-23 0:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 10:35 'git clone,' build makes user non-writable files (should be option keep user-writable) David Chmelik
2022-07-17 11:21 ` Beat Bolli
[not found] ` <YtPtQ6qsIviyTBF2@zbox.drbeat.li>
2022-07-22 13:23 ` David Chmelik
[not found] ` <CAPx1Gvc6ci1CjhL-zjwqkR=4o2yQTrT0V_Hb9bUBNuaBn47M8A@mail.gmail.com>
2022-07-23 0:25 ` David Chmelik [this message]
2022-07-23 3:54 ` Chris Torek
2022-08-02 14:34 ` David Chmelik
2022-08-09 11:05 ` David Chmelik
2022-07-23 4:11 ` Đoàn Trần Công Danh
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ccbc1e81-b406-9e73-7aa5-956ffae7074b@gmail.com \
--to=davidnchmelik@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).