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
