Dusty Pomerleau on Nostr: It seems like it should be possible for our version control systems to have both ...
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.
#git
Published at
2024-07-07 02:51:19Event JSON
{
"id": "4ed18562793bf62e2ac698be45f5f62f81ab13684420196c81ad321704ce26d4",
"pubkey": "5bdfe5c3188a24f76efd37648930d8ada3e458961d03b2e0d62596d4f76e4778",
"created_at": 1720320679,
"kind": 1,
"tags": [
[
"t",
"git"
],
[
"proxy",
"https://fosstodon.org/users/dpom/statuses/112742936068461557",
"activitypub"
]
],
"content": "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 \u003ccommit\u003e` to see all commits squashed into that commit. Basically, allowing commits to nest.\n\n#git",
"sig": "71cf4ab97d5f24a5c95e2d7700c45265a9a002a038fff84f7b1f4f6fad0fca9315e22a1bae4b7b8f7e87895022608666a71118f0999abbda9e2536ddef8e343b"
}
