We won't go into much detail here.Īnd, each one stores some metadata: information such as who made the commit, when, and why (the log message).
1Įach one stores a full snapshot of files.
Lots of Git commands abbreviate these-you can sometimes go as short as the first four characters, 4a0f for instance, as long as that isn't ambiguous, but in a big repository you'll usually need 7 or more characters (and the Linux repository is up to 12 now). There are three big features about commits:Įach one has a unique ID. There's a recurring theme in Git: you make a commit ( git commit), you find a commit (many ways), you show a commit ( git show or sometimes git log), you check out a commit ( git checkout or git switch), and you look through or at commits ( git log again). maybe not so quick) trip through how Git works internally, in this respect.įirst, the big central thing in Git is the commit. I'm confused about what these each do, how they are different, and which one is the answer to my question: To (I hope) help you understand this part, though: Printf "%s %s " $name $(git rev-parse -short $name^)įor extra context, this is the reason I'm asking. git for-each-ref -format='%(refname:short)' -points-at $(git rev-parse refs/stash~1) refs/heads.git log -1 git log -g -no-walk -parents refs/stash.I've seen so many different answers, and I'm confused about what these each do, how they are different, and which one is the answer to my question: How can I reveal the hash of the commit that I was working from when I made that stash (which I guess could be considered a parent commit)? Let's assume that if I run git stash list, I see On featureX: someMessageHere I realize that my question is very similar to How to list the parent commit of a stash in `git stash list` and Get git stash parent commit, but those had so many confusing, disparate responses that I'm asking my own question.
0 kommentar(er)
