From 4d42b2d08bb55f215e62398e6a3d83844e7a3aad Mon Sep 17 00:00:00 2001 From: Kyrylo Yatsenko Date: Fri, 19 Feb 2016 20:43:52 +0200 Subject: [PATCH] =?UTF-8?q?Use=20'half'=20instead=20of=20'=C2=BD'?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- book/10-git-internals/sections/packfiles.asc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/10-git-internals/sections/packfiles.asc b/book/10-git-internals/sections/packfiles.asc index 1d520ef63..f18170484 100644 --- a/book/10-git-internals/sections/packfiles.asc +++ b/book/10-git-internals/sections/packfiles.asc @@ -120,7 +120,7 @@ The other files are your new packfile and an index. The packfile is a single file containing the contents of all the objects that were removed from your filesystem. The index is a file that contains offsets into that packfile so you can quickly seek to a specific object. What is cool is that although the objects on disk before you ran the `gc` were collectively about 15K in size, the new packfile is only 7K. -You've cut your disk usage by ½ by packing your objects. +You've cut your disk usage by half by packing your objects. How does Git do this? When Git packs objects, it looks for files that are named and sized similarly, and stores just the deltas from one version of the file to the next.