git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Marco Costalba <mcostalba@gmail.com>,
	Jon Smirl <jonsmirl@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Why SHA are 40 bytes? (aka looking for flames)
Date: Mon, 23 Apr 2007 22:44:30 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.0.98.0704232236250.12375@xanadu.home> (raw)
In-Reply-To: <462D5370.8040905@zytor.com>

On Mon, 23 Apr 2007, H. Peter Anvin wrote:

> Nicolas Pitre wrote:
> > 
> > Object names aren't 40 bytes.  They are 20 bytes.
> > It  is their hex representation that takes 40 bytes.
> > 
> 
> Sure, but that's the way they're stored in *most* git objects, in particular
> in commit objects.

Commit objects aren't *most* objects.  They usually are blob and tree 
objects, and for the later the SHA1 references are stored as 20 byte 
binary.


Nicolas

      parent reply	other threads:[~2007-04-24  2:44 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
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 [this message]

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=alpine.LFD.0.98.0704232236250.12375@xanadu.home \
    --to=nico@cam.org \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.com \
    --cc=jonsmirl@gmail.com \
    --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).