From: Junio C Hamano <gitster@pobox.com>
To: "Randall S. Becker" <rsbecker@nexbridge.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 08:27:38 -0700 [thread overview]
Message-ID: <xmqqsgpoj6ad.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <006201d55c1a$68180f50$38482df0$@nexbridge.com> (Randall S. Becker's message of "Mon, 26 Aug 2019 10:27:29 -0400")
"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?
next prev parent reply other threads:[~2019-08-26 15:27 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 [this message]
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=xmqqsgpoj6ad.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=albertvaka@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=rsbecker@nexbridge.com \
/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).