Re: 'git clone,' build makes user non-writable files (should be option keep user-writable)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 7/22/22 10:40 AM, Chris Torek wrote:
On Fri, Jul 22, 2022 at 6:24 AM David Chmelik <dchmelik@xxxxxxxxx <mailto:dchmelik@xxxxxxxxx>> 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).



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux