Skip to content

Commit e229d1d

Browse files
authored
note block moved below code block
note block moved below code block
1 parent e2fccb7 commit e229d1d

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

book/10-git-internals/sections/objects.asc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,12 @@ $ git cat-file -p master^{tree}
139139
The `master^{tree}` syntax specifies the tree object that is pointed to by the last commit on your `master` branch.
140140
Notice that the `lib` subdirectory isn't a blob but a pointer to another tree:
141141

142+
[source,console]
143+
----
144+
$ git cat-file -p 99f1a6d12cb4b6f19c8655fca46c3ecf317074e0
145+
100644 blob 47c6340d6459e05787f644c2447d2595f5d3a54b simplegit.rb
146+
----
147+
142148
[NOTE]
143149
====
144150
Depending on what shell you use, you may encounter errors when using the `master^{tree}` syntax.
@@ -148,12 +154,6 @@ In PowerShell or CMD on Windows, the `^` character is used for escaping, so you
148154
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}"`
149155
====
150156

151-
[source,console]
152-
----
153-
$ git cat-file -p 99f1a6d12cb4b6f19c8655fca46c3ecf317074e0
154-
100644 blob 47c6340d6459e05787f644c2447d2595f5d3a54b simplegit.rb
155-
----
156-
157157
Conceptually, the data that Git is storing looks something like this:
158158

159159
.Simple version of the Git data model.

0 commit comments

Comments
 (0)