git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Albert Vaca Cintora <albertvaka@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Michal Suchánek" <msuchanek@suse.de>,
	"Philip Oakley" <philipoakley@iee.email>,
	"Johannes Sixt" <j6t@kdbg.org>,
	git@vger.kernel.org
Subject: Re: [Feature Request] Option to make .git not read-only in cloned repos
Date: Sat, 31 Aug 2019 22:40:20 +0200	[thread overview]
Message-ID: <CAAQViEufHT70-c17hdPqFh4HxB1Wy1dF6huF88P2-n+LWkhamQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqmufqxxof.fsf@gitster-ct.c.googlers.com>

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.

  reply	other threads:[~2019-08-31 20:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23 20:43 [Feature Request] Option to make .git not read-only in cloned repos Albert Vaca Cintora
2019-08-25 11:59 ` Kevin Daudt
2019-08-25 14:39   ` Albert Vaca Cintora
2019-08-25 17:54 ` Johannes Sixt
2019-08-25 19:58   ` Albert Vaca Cintora
2019-08-25 22:41     ` Philip Oakley
2019-08-26 14:38       ` Junio C Hamano
2019-08-26 18:42         ` Albert Vaca Cintora
2019-08-26 19:18           ` SZEDER Gábor
2019-08-27 19:35           ` Junio C Hamano
2019-08-30 12:49             ` Albert Vaca Cintora
2019-08-30 16:38               ` Junio C Hamano
2019-08-30 18:26                 ` Michal Suchánek
2019-08-30 19:25                   ` Junio C Hamano
2019-08-31 20:40                     ` Albert Vaca Cintora [this message]
2019-08-26 14:27     ` Randall S. Becker
2019-08-26 15:27       ` Junio C Hamano
2019-08-26 16:19         ` Randall S. Becker

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=CAAQViEufHT70-c17hdPqFh4HxB1Wy1dF6huF88P2-n+LWkhamQ@mail.gmail.com \
    --to=albertvaka@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=msuchanek@suse.de \
    --cc=philipoakley@iee.email \
    /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).