You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: book/11-git-internals/sections/packfiles.asc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ Wouldn't it be nice if Git could store one of them in full but then the second o
86
86
87
87
It turns out that it can.
88
88
The initial format in which Git saves objects on disk is called a ``loose'' object format.
89
-
However, occasionally Git packs up several of these objects into a single binary file called a packfile in order to save space and be more efficient.
89
+
However, occasionally Git packs up several of these objects into a single binary file called a ``packfile'' in order to save space and be more efficient.
90
90
Git does this if you have too many loose objects around, if you run the `git gc` command manually, or if you push to a remote server.
91
91
To see what happens, you can manually ask Git to pack up the objects by calling the `git gc` command:
0 commit comments