Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Change commands to be more precise #328
will produce the same result when HEAD and master point to the same commit
To make the text more precise and compatible with "last saved commit"
HEAD points specific commits only in a detached state. Naturally, HEAD points to branches (such as master). Because branches are not touched in this lesson, I think it is better to continue to use HEAD. Moreover,
@maxim-belkin, I disagree. Because branches are not touched in this lesson, it is better to provide the command that will not betray the learner's expectations when they (almost inevitably) do encounter branches. The meaning of
It might be worthwhile to also show that one can do
And clarify when those are synonymous and when they aren't (implied: branches matter). A more robust presentation would spend time fleshing out the concept of a
In general, I find we are at odds with the fundamental operation of any DVCS by pushing branching out of scope.