sag@lemm.ee to Programmer Humor@programming.dev · 2 years agoMy Git Knowledgelemm.eeimagemessage-square175fedilinkarrow-up11.13Karrow-down125
arrow-up11.1Karrow-down1imageMy Git Knowledgelemm.eesag@lemm.ee to Programmer Humor@programming.dev · 2 years agomessage-square175fedilink
minus-squarezaphod@lemmy.calinkfedilinkEnglisharrow-up13·2 years 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-squareCyborganism@lemmy.calinkfedilinkarrow-up3·2 years agoRight. I just wanted to keep it as simple as possible.
minus-squarezaphod@lemmy.calinkfedilinkEnglisharrow-up3·2 years 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·2 years agoHonestly I’ve come to realise that being precise is the simplest in the long run
minus-squarespikespaz@programming.devlinkfedilinkarrow-up2·2 years 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.