sag to Programmer [email protected] • 1 year agoMy Git Knowledgelemm.eeimagemessage-square175fedilinkarrow-up11.12K
arrow-up11.12KimageMy Git Knowledgelemm.eesag to Programmer [email protected] • 1 year agomessage-square175fedilink
minus-square@[email protected]linkfedilinkEnglish13•1 year agoFor folks unaware, the technical git term, here, is a ‘ref’. Everything that points to a commit is a ref, whether it’s HEAD, the tip of a branch, or a tag. If the git manpage mentions a ‘ref’ that’s what it’s talking about.
minus-squareCyborganismlinkfedilink3•1 year agoRight. I just wanted to keep it as simple as possible.
minus-square@[email protected]linkfedilink2•1 year agoHonestly I’ve come to realise that being precise is the simplest in the long run
minus-square@[email protected]linkfedilink2•1 year agoPeople get overloaded with words. You have to focus on one concept at a time. Let them ask for others.
minus-square@[email protected]linkfedilinkEnglish3•1 year agoOh, no worries, just figured I’d add that extra little bit of detail as it’s a useful hook into a lot of other git concepts.
For folks unaware, the technical git term, here, is a ‘ref’. Everything that points to a commit is a ref, whether it’s HEAD, the tip of a branch, or a tag. If the git manpage mentions a ‘ref’ that’s what it’s talking about.
Right. I just wanted to keep it as simple as possible.
Honestly I’ve come to realise that being precise is the simplest in the long run
People get overloaded with words. You have to focus on one concept at a time. Let them ask for others.
Oh, no worries, just figured I’d add that extra little bit of detail as it’s a useful hook into a lot of other git concepts.