summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 09eff7b)
raw | patch | inline | side by side (parent: 09eff7b)
author | J. Bruce Fields <bfields@citi.umich.edu> | |
Sun, 9 Sep 2007 02:27:18 +0000 (22:27 -0400) | ||
committer | J. Bruce Fields <bfields@citi.umich.edu> | |
Sun, 16 Sep 2007 02:17:23 +0000 (22:17 -0400) |
Actually I don't think we've previously mentioned .git/objects, so we
need a different introduction here.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
need a different introduction here.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Documentation/user-manual.txt | patch | blob | history |
index 4a0fa7e958a5df016122b0668b08309db158d68c..cf0c188fa5117a0f273fe18bab4debdde96f9aa7 100644 (file)
How git stores objects efficiently: pack files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-We've seen how git stores each object in a file named after the
-object's SHA1 hash.
+Newly created objects are initially created in a file named after the
+object's SHA1 hash (stored in .git/objects).
Unfortunately this system becomes inefficient once a project has a
lot of objects. Try this on an old project: