git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Albert Vaca Cintora <albertvaka@gmail.com>
To: git@vger.kernel.org
Subject: [Feature Request] Option to make .git not read-only in cloned repos
Date: Fri, 23 Aug 2019 22:43:45 +0200	[thread overview]
Message-ID: <CAAQViEsZW4PzHr5BrkDHU2kSd_e04n02McGPgrmXGZMpgaTePg@mail.gmail.com> (raw)

Hi git folks,

Honestly I'm not aware of the reason behind .git being read-only, but
I'm sure there is one.

However, I'm sure that a large percentage of developers out there will
agree with me that having to use force (-f) to delete every cloned
repo is annoying, and even worse, it creates the bad habit of always
force-deleting everything.

Would you find reasonable to add an option to keep .git writable on
cloned repos?

PS: I'm not subscribed to the list, so please CC me on replies.

Thanks!
Albert

             reply	other threads:[~2019-08-23 20:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23 20:43 Albert Vaca Cintora [this message]
2019-08-25 11:59 ` [Feature Request] Option to make .git not read-only in cloned repos 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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAQViEsZW4PzHr5BrkDHU2kSd_e04n02McGPgrmXGZMpgaTePg@mail.gmail.com \
    --to=albertvaka@gmail.com \
    --cc=git@vger.kernel.org \
    /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. 
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 NNTP newsgroup(s).