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@xxxxxxxxxxxxxx> --- Documentation/user-manual.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index 2d7547c..ed623c0 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -2952,8 +2952,8 @@ references in .git/refs/tags/). 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: -- 1.5.3 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
