From: Nikolai Weibull <mailing-lists.git@rawuncut.elitemail.org>
To: git@vger.kernel.org
Subject: Re: git objects directory
Date: Mon, 31 Oct 2005 17:08:03 +0100 [thread overview]
Message-ID: <20051031160803.GB15802@puritan.petwork> (raw)
In-Reply-To: <dk5dgq$isv$1@sea.gmane.org>
Lexington Luthor wrote:
> Can someone please explain why git puts its objects in 256
> sub-directories of objects instead of directly in the objects directory
> itself? I am trying to learn git (actually cogito), but I still don't
> understand why this structure is used.
Because otherwise there would be a lot of objects (files) in the
objects subdirectory, which would cause a lot of problems with many
filesystems.
Anyway, you best leave that directory be, but I understand your desire
to understand :-).
nikolai
--
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
next prev parent reply other threads:[~2005-10-31 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 15:33 git objects directory Lexington Luthor
2005-10-31 16:08 ` Nikolai Weibull [this message]
2005-10-31 16:08 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051031160803.GB15802@puritan.petwork \
--to=mailing-lists.git@rawuncut.elitemail.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).