Re: [Feature Request] Option to make .git not read-only in cloned repos

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 26, 2019, 15:27 UTC
Message-ID: <xmqqsgpoj6ad.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <006201d55c1a$68180f50$38482df0$@nexbridge.com>

"Randall S. Becker" <rsbecker@nexbridge.com> writes:

Show 12 quoted lines

>> Sometimes I clone a repo just to grep for an error string and then I don't
>> need it anymore, or I clone several repos until I find the one that contains
>> what I want and delete the rest. Sometimes I want to write a patch for some
>> software I don't develop regularly so I don't need to keep a clone of it.
>> 
>> In any case, it would be useful to know the reason those files are read-only in
>> the first place. Do you guys know who might know?
>
> Why don't you wrap your clone in a script that calls chmod -R u+w
> .git after the clone? This seems like a pretty trivial approach
> regardless of your workflow. This works in Linux, Mac, Windows
> (under cygwin-bash) and anything else POSIX-ish.

But on anything POSIX-ish, is it a problem for some files (but not any directory) in .git is made read-only?