From: David Srbecky <dsrbecky@gmail.com>
To: git@vger.kernel.org
Subject: Why is the name of a blob SHA1("$type $size\0$data") and not SHA1("$data")?
Date: Thu, 30 Apr 2009 20:55:00 +0100 [thread overview]
Message-ID: <49FA0214.70009@gmail.com> (raw)
Hi,
First of all, congratulations on makeing such a great version control
system. I love the storage model - in comparison with other systems, it
is just birantly simple and ingenious.
I started digging into the details and there is one thing that is really
bugging me - why is the name of a blob SHA1("$type $size\0$data") and
not SHA1("$data")? I mean, wouldn't it be beautiful if the name of the
blob would really just be the SHA1 of the uncompressed file content? :-)
Furthermore, is the header really necessary? Wouldn't it be
eqvivalently effective to put the blobs into own subdirectory? For
example: .git\objects\blob\22\22a3d28c5b2fca0eae83be1a2ed619e357f6a1e6
So the blob would contatin just be the compressed content and nothing
else - beautiful :-)
I would really appriciate some comments on the design decisions so that
I can sleep well at night :-)
David
next reply other threads:[~2009-04-30 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 19:55 David Srbecky [this message]
2009-04-30 20:02 ` Why is the name of a blob SHA1("$type $size\0$data") and not SHA1("$data")? Shawn O. Pearce
2009-04-30 22:57 ` Björn Steinbrink
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=49FA0214.70009@gmail.com \
--to=dsrbecky@gmail.com \
--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).