Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL So 07.07.2024 00:00:04 61.917 0 3.522.885 56,9 Fosstodon 4.2.10 500 Sa 06.07.2024 00:00:07 61.917 -2 3.523.632 56,9 Fosstodon 4.2.10 500 Fr 05.07.2024 00:00:27 61.919 0 3.520.710 56,9 Fosstodon 4.2.10 500 Do 04.07.2024 00:00:52 61.919 +2 3.517.337 56,8 Fosstodon 4.2.9 500 Mi 03.07.2024 00:00:12 61.917 +2 3.513.906 56,8 Fosstodon 4.2.9 500 Di 02.07.2024 00:01:44 61.915 -2 3.510.479 56,7 Fosstodon 4.2.9 500 Mo 01.07.2024 00:00:33 61.917 0 3.507.420 56,6 Fosstodon 4.2.9 500 So 30.06.2024 00:00:34 61.917 +2 3.504.671 56,6 Fosstodon 4.2.9 500 Sa 29.06.2024 00:01:13 61.915 +2 3.501.982 56,6 Fosstodon 4.2.9 500 Fr 28.06.2024 00:01:07 61.913 0 3.498.459 56,5 Fosstodon 4.2.9 500
Dusty Pomerleau (@dpom) · 11/2022 · Tröts: 1.357 · Folger: 126
So 07.07.2024 04:51
It seems like it should be possible for our version control systems to have both Squash and Expand (meaning, lossless squashing). It would allow a collapsed commit history to appear "clean" and yet not lose any history. In some sense, `jj operation log` already permits this (`git reflog` would only work locally), but what I'm envisioning is the ability to simply call `git log --expand <commit>` to see all commits squashed into that commit. Basically, allowing commits to nest.
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0