SagXD@lemm.ee to Programmer Humor@programming.dev · 7 months agoMy Git Knowledgelemm.eeimagemessage-square178fedilinkarrow-up11.12Karrow-down125
arrow-up11.09Karrow-down1imageMy Git Knowledgelemm.eeSagXD@lemm.ee to Programmer Humor@programming.dev · 7 months agomessage-square178fedilink
minus-squarezaphodlinkfedilinkEnglisharrow-up13·7 months 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-squareCyborganismlinkfedilinkarrow-up3·7 months agoRight. I just wanted to keep it as simple as possible.
minus-squarezaphodlinkfedilinkEnglisharrow-up3·7 months 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.
minus-squareembed_me@programming.devlinkfedilinkarrow-up2·7 months agoHonestly I’ve come to realise that being precise is the simplest in the long run
minus-squarespikespaz@programming.devlinkfedilinkarrow-up2·7 months agoPeople get overloaded with words. You have to focus on one concept at a time. Let them ask for others.
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.
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.
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.