From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: "Marco Costalba" <mcostalba@gmail.com>
Subject: Re: Why SHA are 40 bytes? (aka looking for flames)
Date: Sat, 21 Apr 2007 16:08:01 +0100 [thread overview]
Message-ID: <200704211608.06171.andyparkins@gmail.com> (raw)
In-Reply-To: <e5bfff550704210635r4008c3c6tf5f55f970bf85e44@mail.gmail.com>
On Saturday 2007, April 21, Marco Costalba wrote:
> Well, why to store always the full length SHA?
Well apart from being easier than working out the optimum size for every
single object write, one really good reason would be that there is no
way to predict that an object in the future won't have a conflicting
SHA - every object /has/ to be stored with its full hash, because you
are preventing conflicts with everything object now, in the past and
all possible futures.
Wow - git is like a time machine.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-04-21 15:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-21 13:35 Why SHA are 40 bytes? (aka looking for flames) Marco Costalba
2007-04-21 15:08 ` Andy Parkins [this message]
2007-04-21 16:53 ` Karl Hasselström
2007-04-21 17:09 ` Marco Costalba
2007-04-21 16:58 ` Marco Costalba
2007-04-21 15:37 ` Jon Smirl
2007-04-21 17:06 ` Marco Costalba
2007-04-21 17:59 ` Jon Smirl
2007-04-21 18:28 ` Marco Costalba
2007-04-21 19:36 ` Jon Smirl
2007-04-24 14:48 ` Andreas Ericsson
2007-04-24 15:04 ` Nicolas Pitre
2007-04-24 15:18 ` Andreas Ericsson
2007-04-24 16:19 ` Nicolas Pitre
2007-04-22 13:27 ` Nicolas Pitre
2007-04-24 0:46 ` H. Peter Anvin
2007-04-24 2:30 ` Shawn O. Pearce
2007-04-24 2:44 ` Nicolas Pitre
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=200704211608.06171.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=mcostalba@gmail.com \
/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).