All of lore.kernel.org
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Albert Vaca Cintora <albertvaka@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	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: Mon, 26 Aug 2019 21:18:40 +0200	[thread overview]
Message-ID: <20190826191840.GS20404@szeder.dev> (raw)
In-Reply-To: <CAAQViEsL+X5ZYmmSjG1JBksGjthHCUyWa3525b8dN7u1XAbvJg@mail.gmail.com>

On Mon, Aug 26, 2019 at 08:42:56PM +0200, Albert Vaca Cintora wrote:
> > Why don't you wrap your clone in a script that calls chmod -R u+w .git after the clone? This seems like a pretty trivial approach regardless of your workflow. This works in Linux, Mac, Windows (under cygwin-bash) and anything else POSIX-ish.
> >
> 
> Wrapping `git clone` should work as a workaround. Although if that
> doesn't break anything... then why were those files read-only in the
> first place? :)

Those read-only object and pack files contain all the version history,
and, therefore, are precious.  Making them read-only can protect
from accidental deletion.

> The fact that, from a formal point of view, those files are immutable
> doesn't seem to justify them being read-only (or, at least, doesn't
> follow any convention): there are plenty of immutable files on any
> system (eg: all binaries and libs, application assets like images and
> icons, pid/lock files for daemons, etc.) that are not made read-only.

None of those files are actually immutable: the next update will
overwrite the binaries, libs, and assets, stopping the daemon will
remove the pidfile.

OTOH, Git's object and pack files are indeed immutable.


  reply	other threads:[~2019-08-26 19:18 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 [this message]
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=20190826191840.GS20404@szeder.dev \
    --to=szeder.dev@gmail.com \
    --cc=albertvaka@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.