File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -197,10 +197,10 @@ stages:
197
197
The path for the object with the hash `e88f7a929cd70b0274c4ea33b209c97fa845fdbc` would be:
198
198
199
199
```bash
200
- ./. git/objects/e8/8f7a929cd70b0274c4ea33b209c97fa845fdbc
200
+ .git/objects/e8/8f7a929cd70b0274c4ea33b209c97fa845fdbc
201
201
```
202
202
203
- You'll see that the file isn't placed directly in the `./ git/objects` directory. Instead, it's placed in a directory named with the
203
+ You'll see that the file isn't placed directly in the `.git/objects` directory. Instead, it's placed in a directory named with the
204
204
first two characters of the object's hash. The remaining 38 characters are used as the file name.
205
205
206
206
Each Git object has its own format for storage. We'll look at how Blobs are stored in this stage, and we'll cover
@@ -548,7 +548,7 @@ stages:
548
548
<summary>Click to expand/collapse</summary>
549
549
550
550
Just like blobs, tree objects are stored in the `.git/objects` directory. If the hash of a tree object is `e88f7a929cd70b0274c4ea33b209c97fa845fdbc`,
551
- the path to the object would be `./ git/objects/e8/8f7a929cd70b0274c4ea33b209c97fa845fdbc`.
551
+ the path to the object would be `.git/objects/e8/8f7a929cd70b0274c4ea33b209c97fa845fdbc`.
552
552
553
553
The format of a tree object file looks like this (after Zlib decompression):
554
554
You can’t perform that action at this time.
0 commit comments