Weird or confusing #Git terms? I for one had no big problems with HEAD[1]. But for some strange reason another one caused me confusion for a long time:
"origin"
Sometimes I think Git should force users to name a remote when cloning a repo, as I guess it would make grasping the concept of Git remotes quite a bit easier for some people.
[1] @b0rk called it "weird" recently here: https://social.jvns.ca/@b0rk/111942019
Thorsten Leemhuis (acct. 1/4) /
npub1fz…emju7
2024-03-05 10:23:32
Author Public Key
npub1fzflkuaynm4r0fgzxpjky4t3266gm8es3cw34xtmlczwa3wt70us6emju7Published at
2024-03-05 10:23:32Event JSON
{
"id": "fe326337e704a0762079a0aeb3e0b5b3472a1cdc58ef01f40796df26bef69ee0",
"pubkey": "4893fb73a49eea37a502306562557156b48d9f308e1d1a997bfe04eec5cbf3f9",
"created_at": 1709634212,
"kind": 1,
"tags": [
[
"t",
"git"
],
[
"proxy",
"https://fosstodon.org/users/kernellogger/statuses/112042587764975845",
"activitypub"
]
],
"content": "Weird or confusing #Git terms? I for one had no big problems with HEAD[1]. But for some strange reason another one caused me confusion for a long time:\n\n\"origin\"\n\nSometimes I think Git should force users to name a remote when cloning a repo, as I guess it would make grasping the concept of Git remotes quite a bit easier for some people.\n\n[1] @b0rk called it \"weird\" recently here: https://social.jvns.ca/@b0rk/111942019",
"sig": "304accbccb8f4f417c6e25dfb3e298b3ce6c49497b4b3f197ee7686b93cf4bd2932590d9098962095277d2ff06068437b9793b81577a8ab11df227979b8ea69e"
}