From: David Chmelik <dchmelik@gmail.com>
To: git@vger.kernel.org
Subject: 'git clone,' build makes user non-writable files (should be option keep user-writable)
Date: Fri, 15 Jul 2022 03:35:49 -0700 [thread overview]
Message-ID: <822787da-bc26-0d72-a5c4-808a3d10126e@gmail.com> (raw)
What did you do before the bug happened?
'git clone,' built various software (with gcc, BSD & GNU make,
autotools, cmake, etc.)
What did you expect to happen?
Option: keep cloned/built/etc. files user-writable.
What happened instead?
Needed chmod or 'sudo rm -rf.'
What's different between what you expected and what actually happened?
Option: keep cloned/built/etc. files user-writable, otherwise (has been
said 15+ years) encourages 'sudo rm -rf.'
Anything else you want to add:
I try/test/debug (and report bugs) many software commits but
don't commit so need cloned/built/etc. files writable as user & even
system-wide options: who hasn't made 'rm -rf' mistakes? (unrelated but
someone might claim is: I don't use non-UNIX-like OS that shell alias
'rm -rf' to confirm every file (potentially thousands) and though made
my own alias (confirm once) it's longer, sometimes unavailable so don't
always use (many people don't)... software should always have
user-writable files option.) Below indicates GNU/Linux but also have
often used git on *BSD/Unix. I'm not on git mailing list but you can CC
me all replies.
[System Info]
git version:
git version 2.37.1
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 5.18.11 #1 SMP PREEMPT_DYNAMIC Wed Jul 13 00:20:29 CDT 2022
x86_64
compiler info: gnuc: 12.1
libc info: glibc: 2.35
$SHELL (typically, interactive shell): /bin/bash
next reply other threads:[~2022-07-15 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 10:35 David Chmelik [this message]
2022-07-17 11:21 ` 'git clone,' build makes user non-writable files (should be option keep user-writable) Beat Bolli
[not found] ` <YtPtQ6qsIviyTBF2@zbox.drbeat.li>
2022-07-22 13:23 ` David Chmelik
[not found] ` <CAPx1Gvc6ci1CjhL-zjwqkR=4o2yQTrT0V_Hb9bUBNuaBn47M8A@mail.gmail.com>
2022-07-23 0:25 ` David Chmelik
2022-07-23 3:54 ` Chris Torek
2022-08-02 14:34 ` David Chmelik
2022-08-09 11:05 ` David Chmelik
2022-07-23 4:11 ` Đoàn Trần Công Danh
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=822787da-bc26-0d72-a5c4-808a3d10126e@gmail.com \
--to=dchmelik@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.
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).