sag@lemm.ee to Programmer Humor@programming.dev · 1 年前My Git Knowledgelemm.eeimagemessage-square177fedilinkarrow-up11.13Karrow-down125
arrow-up11.1Karrow-down1imageMy Git Knowledgelemm.eesag@lemm.ee to Programmer Humor@programming.dev · 1 年前message-square177fedilink
minus-squarezaphod@lemmy.calinkfedilinkEnglisharrow-up13·1 年前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.
minus-squareCyborganism@lemmy.calinkfedilinkarrow-up3·1 年前Right. I just wanted to keep it as simple as possible.
minus-squarezaphod@lemmy.calinkfedilinkEnglisharrow-up3·1 年前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.
minus-squareembed_me@programming.devlinkfedilinkarrow-up2·1 年前Honestly I’ve come to realise that being precise is the simplest in the long run
minus-squarespikespaz@programming.devlinkfedilinkarrow-up2·1 年前People 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.