Timeline for cp command follows symbolic link at destination and clobbers link target instead of overwriting link
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 26, 2022 at 21:12 | history | edited | Kusalananda♦ | CC BY-SA 4.0 |
Reformulate, spell words out, markup and general cleanup.
|
| Oct 9, 2021 at 20:45 | history | edited | Jeff Schaller♦ | CC BY-SA 4.0 |
added 3 characters in body
|
| Sep 2, 2021 at 17:09 | vote | accept | SurpriseDog | ||
| Sep 2, 2021 at 17:07 | comment | added | SurpriseDog | @MechMK1 Another reason why everytime I've started a script in bash, I end up regretting it and switching to Python. It just works and it works across platforms and any utility I need, I can call with subprocess | |
| Sep 2, 2021 at 14:38 | comment | added | MechMK1 | This, coincidentally, is also the reason why build scripts test exactly how the locally installed version of some executable behaves in specific circumstances. | |
| Sep 2, 2021 at 0:48 | history | became hot network question | |||
| Sep 1, 2021 at 18:45 | answer | added | usretc | timeline score: 3 | |
| Sep 1, 2021 at 17:18 | answer | added | Kusalananda♦ | timeline score: 22 | |
| Sep 1, 2021 at 16:48 | history | asked | SurpriseDog | CC BY-SA 4.0 |