From 0a8ee526489e44d49e1d81697c33502a13619745 Mon Sep 17 00:00:00 2001 From: Seth Fitzsimmons Date: Tue, 29 Nov 2011 17:45:01 +0000 Subject: [PATCH] =?UTF-8?q?Typo:=20seperate=20=E2=86=92=20separate?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../0_ How_Git_Stores_Objects.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/text/48_How_Git_Stores_Objects/0_ How_Git_Stores_Objects.markdown b/text/48_How_Git_Stores_Objects/0_ How_Git_Stores_Objects.markdown index f7a03d61..e469dd16 100644 --- a/text/48_How_Git_Stores_Objects/0_ How_Git_Stores_Objects.markdown +++ b/text/48_How_Git_Stores_Objects/0_ How_Git_Stores_Objects.markdown @@ -11,7 +11,7 @@ packed objects. ### Loose Objects ### Loose objects are the simpler format. It is simply the compressed data stored -in a single file on disk. Every object written to a seperate file. +in a single file on disk. Every object written to a separate file. If the sha of your object is ab04d884140f7b0cf8bbf86d6883869f16a46f65, then the file will be stored in the following path: @@ -49,7 +49,7 @@ implementation of object storage: ### Packed Objects ### The other format for object storage is the packfile. Since Git stores each -version of each file as a seperate object, it can get pretty inefficient. +version of each file as a separate object, it can get pretty inefficient. Imagine having a file several thousand lines long and changing a single line. Git will store the second file in it's entirety, which is a great big waste of space.