git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Witten <mfwitten@gmail.com>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
	David Abrahams <dave@boostpro.com>, Jeff King <peff@peff.net>,
	Daniel Barkalow <barkalow@iabervon.org>,
	Johan Herland <johan@herland.net>,
	git@vger.kernel.org, "J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: Lets avoid the SHA-1 term (was [doc] User Manual Suggestion)
Date: Mon, 27 Apr 2009 08:02:02 -0500	[thread overview]
Message-ID: <b4087cc50904270602q17fba432ka219180d358fae47@mail.gmail.com> (raw)
In-Reply-To: <20090427002838.GF12338@atjola.homenet>

2009/4/26 Björn Steinbrink <B.Steinbrink@gmx.de>:
>
>> Do you agree that either 'id' or 'hash' would work fine?
>
> "object id" would work for me, but I'm fine with the existing "object
> name" as well. I don't like "object hash" (or "object hash id"), because
> it IMHO doesn't express that well that it's used to identify an object.

However, the SHA-1 hash is not actually essential to git. In the git
world, there is only content and every object is identified by its
content. Now, to identify an object, it would be pretty cumbersome to
have to write out the contents, so we abbreviate the contents with a
hash.

So, the hash or object name or object id or whatever you want to call
it isn't even an essential part to git. It is a convenience.

In that sense, I think that '[cryptographic] hash' is the right term,
because the others ("object name" and "object id") seem special. A
hash is not special. In fact, the documentation should read "For
convenience, the git tools refer to objects using the hash value of
their contents". You see? It's not essential.

  reply	other threads:[~2009-04-27 13:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26 23:38 Lets avoid the SHA-1 term (was [doc] User Manual Suggestion) Felipe Contreras
2009-04-27  0:28 ` Björn Steinbrink
2009-04-27 13:02   ` Michael Witten [this message]
2009-05-02 15:37     ` Björn Steinbrink
2009-04-27 12:06 ` Michael J Gruber

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=b4087cc50904270602q17fba432ka219180d358fae47@mail.gmail.com \
    --to=mfwitten@gmail.com \
    --cc=B.Steinbrink@gmx.de \
    --cc=barkalow@iabervon.org \
    --cc=bfields@fieldses.org \
    --cc=dave@boostpro.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johan@herland.net \
    --cc=peff@peff.net \
    /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).