Changes between Version 10 and Version 11 of versionControl/git

Timestamp:

Jul 12, 2016 12:02:03 PM (6 years ago)

Author:

juaco

Comment:

--

versionControl/git

@@ -296 +296 @@
 
 
-{{{git reset}}} as the dangerous method. When you undo with {{{git reset}}}(and the commits are no longer referenced by any ref or the reflog), there is no way to retrieve the original copy—it is a permanent undo. 
+{{{git reset}}} is a dangerous method. When you undo with {{{git reset}}} (and the commits are no longer referenced by any ref or the reflog), there is no way to retrieve the original copy—it is a permanent undo. 
 
 Remove the specified file from the staging area, but leave the working directory unchanged. This unstages a file without overwriting any changes.
@@ -429 +429 @@
 
 
+==== Getting back to the latest commit 
+
+If you know the commit you want to return to is the head of some branch (the default is usually the `master` branch), or is tagged, then you can just
+
+{{{
+git checkout <branchname>
+}}}
+
+Another useful command is `git reflog`, to see what other commits your `HEAD` (or any other ref) has pointed to in the past.
+
+{{{
+git reflog
+}}}
+
+This is different than `git log` because it lists the hole history, and not just the strictly the antecedent events.
+
+
 == Git Branches ==