git cat-file -p master^{tree} in other shells #1011
Conversation
usage of git cat-file -p master^{tree} command in other shells as specified in this answer https://stackoverflow.com/a/17121954/2445295 thanks to @Mellbourn
| The `master^{tree}` syntax specifies the tree object that is pointed to by the last commit on your `master` branch. | ||
| Notice that the `lib` subdirectory isn't a blob but a pointer to another tree: | ||
|
|
||
| **NOTE**: while using `master^{tree}` syntax if you have error try the following |
There was a problem hiding this comment.
Instead of just setting this in bold-face, let's use the Asciidoc "note" feature:
[NOTE]
====
(Note content goes here)
====This will render much nicer.
In addition, let's change the prose here to read like this:
Depending on what shell you use, you may encounter errors when using the `master^{tree}` syntax.
In PowerShell or CMD on Windows, the `^` character is used for escaping, so you have to double it to avoid this: `git cat-file -p master^^{tree}`.
If you're using ZSH, the `^` character is used for globbing, so you have to enclose the whole expression in quotes: `git cat-file -p "master^{tree}"`.Or something like that. It's a bit more idiomatically English.
NOTE heading style changed and its content rephrased
| ==== | ||
| * Depending on what shell you use, you may encounter errors when using the `master^{tree}` syntax | ||
| * In PowerShell or CMD on Windows, the `^` character is used for escaping, so you have to double it to avoid this: `git cat-file -p mater^^{tree}` | ||
| * If you're using ZSH, the `^` character is used for globbing, so you have to enclose the whole expression in quotes: `git cat-file -p "master^{tree}"` |
There was a problem hiding this comment.
Interesting. Why did you set this using bullets?
Let's just write it as a single paragraph, I think that flows better.
list converted to single paragraph
|
|
||
| [NOTE] | ||
| ==== | ||
| Depending on what shell you use, you may encounter errors when using the `master^{tree}` syntax. In PowerShell or CMD on Windows, the `^` character is used for escaping, so you have to double it to avoid this: `git cat-file -p mater^^{tree}`. If you're using ZSH, the `^` character is used for globbing, so you have to enclose the whole expression in quotes: `git cat-file -p "master^{tree}"` |
There was a problem hiding this comment.
Sorry, one more request: could you reformat this with one sentence on each source-code line? It makes reviewing PRs much easier in the future.
changed to one sentence on each source-code line
| If you're using ZSH, the `^` character is used for globbing, so you have to enclose the whole expression in quotes: `git cat-file -p "master^{tree}"` | ||
| ==== | ||
|
|
There was a problem hiding this comment.
Oh man, I hate to do this to you again, but I have one last request (I promise). Looking at how this renders in context:
The "here's what you should do, and here's what it looks like when you do it" flow is interrupted by this note block. Could you move it just below the code block?
There was a problem hiding this comment.
Hope these formatting rules are defined somewhere so that people could just read and follow it.
note block moved below code block
usage of
git cat-file -p master^{tree} commandin other environments as specified in this answer https://stackoverflow.com/a/17121954/2445295 thanks to @Mellbourn