From: Simon Ruderich <simon@ruderich.org>
To: Thomas Ackermann <th.acker@arcor.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 2/3] glossary: improve description of SHA-1 related topics
Date: Sun, 7 Apr 2013 21:14:07 +0200 [thread overview]
Message-ID: <20130407191407.GA13708@ruderich.org> (raw)
In-Reply-To: <824604721.1719644.1365347429662.JavaMail.ngmail@webmail09.arcor-online.net>
On Sun, Apr 07, 2013 at 05:10:29PM +0200, Thomas Ackermann wrote:
> Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
> ---
> [snip]
>
> [[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
> + object name is usually represented by a 40 character
> + hexadecimal string. Also colloquially called <<def_SHA1,SHA-1>>
^
Trailing . missing.
Regards
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
next prev parent reply other threads:[~2013-04-07 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 15:06 [PATCH v2 0/3] Some small fixes to glossary-content.txt Thomas Ackermann
2013-04-07 15:09 ` [PATCH v2 1/3] glossary: remove outdated/misleading/irrelevant entries Thomas Ackermann
2013-04-07 17:24 ` Junio C Hamano
2013-04-07 15:10 ` [PATCH v2 2/3] glossary: improve description of SHA-1 related topics Thomas Ackermann
2013-04-07 17:24 ` Junio C Hamano
2013-04-07 19:14 ` Simon Ruderich [this message]
2013-04-07 15:11 ` [PATCH v2 3/3] glossary: remove definition of refspec and pathspec Thomas Ackermann
2013-04-07 17:25 ` Junio C Hamano
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=20130407191407.GA13708@ruderich.org \
--to=simon@ruderich.org \
--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).