Skip to content

Add note on PowerShell in Revision Selection #1518

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 25, 2020
Merged

Add note on PowerShell in Revision Selection #1518

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
edf81f0
Add note in Revision Selection about PowerShell
vegar Sep 9, 2020
e16291c
Improve language
vegar Sep 9, 2020
b9129ed
Remove reference to Windows
vegar Sep 9, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions book/07-git-tools/sections/revision-selection.asc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down