[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Re: [Feature Request] Option to make .git not read-only in cloned repos
From:       Albert Vaca Cintora <albertvaka () gmail ! com>
Date:       2019-08-31 20:40:20
Message-ID: CAAQViEufHT70-c17hdPqFh4HxB1Wy1dF6huF88P2-n+LWkhamQ () mail ! gmail ! com
[Download RAW message or body]

On Fri, Aug 30, 2019 at 9:25 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> 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.

I would permanently enable --no-read-only-file-in-git for all newly
cloned repositories (via an alias, or .gitconfig if possible), so
there would be no need to type it every time.
[prev in list] [next in list] [prev in thread] [next in thread]