git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Thomas Ackermann <th.acker@arcor.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/3] Improve description of SHA1 related topics in glossary-content.txt
Date: Tue, 02 Apr 2013 09:05:07 -0700	[thread overview]
Message-ID: <7v38v8hqa4.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <638015718.727691.1364894866964.JavaMail.ngmail@webmail14.arcor-online.net> (Thomas Ackermann's message of "Tue, 2 Apr 2013 11:27:46 +0200 (CEST)")

Thomas Ackermann <th.acker@arcor.de> writes:

> Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
> ---
>  Documentation/glossary-content.txt | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
> index ab02238..05bfebc 100644
> --- a/Documentation/glossary-content.txt
> +++ b/Documentation/glossary-content.txt
> @@ -146,7 +146,7 @@ to point at the new commit.
>  	created. Configured via the `.git/info/grafts` file.
>  
>  [[def_hash]]hash::
> -	In Git's context, synonym to <<def_object_name,object name>>.
> +	In Git's context, synonym for <<def_object_name,object name>>.

OK.

>  [[def_object_name]]object name::
> -	The unique identifier of an <<def_object,object>>. The <<def_hash,hash>>
> -	of the object's contents using the Secure Hash Algorithm
> -	1 and usually represented by the 40 character hexadecimal encoding of
> -	the <<def_hash,hash>> of the object.
> +	The unique identifier of an <<def_object,object>>: The <<def_SHA1,SHA1>> hash
> +	of the object's contents. The object name is usually represented by the 
> +	40 character hexadecimal encoding of the hash value.

I am torn on this one.  When you have a file A on the filesystem,
the object name of the blob that records the contents of that file
is *not* the same as output from "sha1sum A".

I doubt we should spell out _how_ it is computed.  In the glossary,
it is better to say what it is and what it is used for; the tutorial
and Documentation/technical/ give better details that the readers
who refer to the glossary do not need.

	The unique identifier of an <<def_object,object>>.  The
	object name is usually represented by a 40 character
	hexadecimal string.  Also colloquially called
	<<def_SHA1,SHA-1>>.

might be sufficient.

> @@ -426,7 +425,8 @@ should not be combined with other pathspec.
>  	Source code management (tool).
>  
>  [[def_SHA1]]SHA1::
> -	Synonym for <<def_object_name,object name>>.
> +	"Secure Hash Algorithm 1"; a cryptographic hash function. 
> +	In the context of Git used as a synonym for <<def_object_name,object name>>.

We should spell it as "SHA-1" with a dash.

  reply	other threads:[~2013-04-02 16:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02  9:24 [PATCH 0/3] Some small fixes to glossary-content.txt Thomas Ackermann
2013-04-02  9:26 ` [PATCH 1/3] Remove outdated/missleading/irrelevant entries from glossary-content.txt Thomas Ackermann
2013-04-02 15:56   ` Junio C Hamano
2013-04-02  9:27 ` [PATCH 2/3] Improve description of SHA1 related topics in glossary-content.txt Thomas Ackermann
2013-04-02 16:05   ` Junio C Hamano [this message]
2013-04-02  9:28 ` [PATCH 3/3] Remove definition of refspec and pathspec from glossary-content.txt Thomas Ackermann
2013-04-02 16:08   ` Junio C Hamano
2013-04-02 17:05   ` Aw: " Thomas Ackermann
2013-04-02 17:23     ` Junio C Hamano
2013-04-02 17:34     ` Aw: " Thomas Ackermann
2013-04-02 15:48 ` [PATCH 0/3] Some small fixes to glossary-content.txt Junio C Hamano
2013-04-06  8:00 ` Aw: " Thomas Ackermann

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=7v38v8hqa4.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=th.acker@arcor.de \
    /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).