From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>
Cc: "'Albert Vaca Cintora'" <albertvaka@gmail.com>,
"'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 12:19:22 -0400 [thread overview]
Message-ID: <008e01d55c2a$08749ea0$195ddbe0$@nexbridge.com> (raw)
In-Reply-To: <xmqqsgpoj6ad.fsf@gitster-ct.c.googlers.com>
On August 26, 2019 11:28 AM, Junio C Hamano wrote:
> "Randall S. Becker" <rsbecker@nexbridge.com> writes:
>
> >> Sometimes I clone a repo just to grep for an error string and then I
> >> don't need it anymore, or I clone several repos until I find the one
> >> that contains what I want and delete the rest. Sometimes I want to
> >> write a patch for some software I don't develop regularly so I don't
need
> to keep a clone of it.
> >>
> >> In any case, it would be useful to know the reason those files are
> >> read-only in the first place. Do you guys know who might know?
> >
> > 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.
>
> But on anything POSIX-ish, is it a problem for some files (but not any
> directory) in .git is made read-only?
Not for me or anyone I personally support. As I suggested to Albert,
wrapping a clone in a script with a chmod would solve the problem with
minimal work.
My own personal issue is convincing people not to clone for every topic
branch, but that's unrelated.
prev parent reply other threads:[~2019-08-26 16:19 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
2019-08-26 14:27 ` Randall S. Becker
2019-08-26 15:27 ` Junio C Hamano
2019-08-26 16:19 ` Randall S. Becker [this message]
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='008e01d55c2a$08749ea0$195ddbe0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=albertvaka@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.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 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.