because we have a bunch of rules and expectations around branches like
* commits that aren't on a branch are almost impossible to see in git (without the reflog), so why would you put them on a diagram?
* commits that aren't on a branch get GC'd eventually
* having 2 branches that point to the same commit is of course possible but feels redundant in most cases
* having a branch that points at an ancestor of another branch is a bit weird (but more common)
(3/?)
Julia Evans /
npub1ym…nlm9y
2023-11-21 01:19:53
in reply to nevent1q…4es6
Author Public Key
npub1ym9ddu2qh7rda8pxklq4gxw2kxhtm4cgvdvdy64z6agwy88nhuhqcnlm9yPublished at
2023-11-21 01:19:53Event JSON
{
"id": "a98f243673ae39356bf6b2f6dcbb0f5d374301e3a483a907b192b37ede9368ff",
"pubkey": "26cad6f140bf86de9c26b7c15419cab1aebdd7086358d26aa2d750e21cf3bf2e",
"created_at": 1700529593,
"kind": 1,
"tags": [
[
"e",
"a540738b6d8a7f14f49a6a278a5e28b7409fe77b56a095eadc8a33236ac158aa",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://social.jvns.ca/users/b0rk/statuses/111445907434614946",
"activitypub"
]
],
"content": "because we have a bunch of rules and expectations around branches like\n\n* commits that aren't on a branch are almost impossible to see in git (without the reflog), so why would you put them on a diagram?\n* commits that aren't on a branch get GC'd eventually\n* having 2 branches that point to the same commit is of course possible but feels redundant in most cases\n* having a branch that points at an ancestor of another branch is a bit weird (but more common)\n\n(3/?)",
"sig": "4851d5297bc354ddb6007c63a47b69b4a623229ff2bb2308d8ef126a5cfaeabef69eb7b01f689a428ae76f8cefd0918b7551bed019aa32e27e72e0c4a07ac1b8"
}