From: Junio C Hamano <gitster@pobox.com>
To: Albert Vaca Cintora <albertvaka@gmail.com>
Cc: 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: Fri, 30 Aug 2019 09:38:11 -0700 [thread overview]
Message-ID: <xmqqd0gmzk0c.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAAQViEv1wWGTzQ29t0qi9rYoRY=Y86GL7E5rR4XySOBoeRx2pg@mail.gmail.com> (Albert Vaca Cintora's message of "Fri, 30 Aug 2019 14:49:30 +0200")
Albert Vaca Cintora <albertvaka@gmail.com> writes:
> On Tue, Aug 27, 2019 at 9:35 PM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> Ah, your "rm" command needs to learn "-f" option, too, then?
>
> The whole point of this thread was to remove the need of -f forcing the removal.
OK, I misunderstood what you wanted to do.
If an implementation of Git were making everything under .git/
read-only, including directories, then it is veriy much reasonable
to complain against such an implementation. The usual "I know I am
doing something unusual and forcing it" safety given by "rm -rf" is
not enough to remove such a clone, and user would need "chmod -R u+w"
beforehand to be able to remove---that is being unreasonably paranoid
in the name of protecting against mistakes.
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?
next prev parent reply other threads:[~2019-08-30 16:38 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 [this message]
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
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=xmqqd0gmzk0c.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=albertvaka@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--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).