From: Junio C Hamano Date: Fri, 30 Aug 2019 19:25:52 GMT Subject: Re: [Feature Request] Option to make .git not read-only in cloned repos Message-ID: In-Reply-To: <20190830202635.0bc7e14f@kitsune.suse.cz> Michal Suchánek writes: >> But requiring an additional single "f" when doing "rm -rf .git"? Is >> that realy too much of a hassle? The option "-f" is to allow people >> deal with an unusual situation, while preventing everyday use from >> doing something harmful unintendedly. And removing a cloned >> repository is an unusual situation that would not happen every day, >> no? > ... > I am not in this situation so often but indeed I sometimes clone > several repositories in a day to search for a patch or piece of code > and then don't need them anymore. Some people may be in such situation > more often or regularly. But between these two: $ git clone --no-read-only-file-in-git https://github.com/foo/bar ...sightsee... $ rm -r bar to avoid "f" in "rm -r", vs. $ git clone https://github.com/foo/bar ...sightsee... $ rm -rf bar to clone a repository you only have a tentive interest in just like any other more permanent repositories, I am not sure how the former is preferrable.