Merge pull request #1518 from vegar/patch-1

Author: ben

book/07-git-tools/sections/revision-selection.asc

@@ -180,6 +180,22 @@ Running `git show HEAD@{2.months.ago}` will show you the matching commit only if
 If you have a UNIX or Linux background, you can think of the reflog as Git's version of shell history, which emphasizes that what's there is clearly relevant only for you and your ``session'', and has nothing to do with anyone else who might be working on the same machine.
 ====
 
+[NOTE]
+.Escaping braces in PowerShell
+====
+
+When using PowerShell, braces like `{` and `}` are special characters and must be escaped.
+You can escape them with a backtick ` or put the commit reference in quotes:
+
+[source,console]
+----
+$ git show HEAD@{0}     # will NOT work
+$ git show HEAD@`{0`}   # OK
+$ git show "HEAD@{0}"   # OK
+----
+
+====
+
 ==== Ancestry References
 
 The other main way to specify a commit is via its ancestry.