From: Daniel Barkalow <barkalow@iabervon.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Petr Baudis <pasky@suse.cz>,
"J. Bruce Fields" <bfields@fieldses.org>,
kha@treskal.com, junio@cox.net, git@vger.kernel.org
Subject: Re: [PATCH] Add a birdview-on-the-source-code section to the user manual
Date: Wed, 9 May 2007 12:18:53 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705091210570.18541@iabervon.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705091447110.4167@racer.site>
On Wed, 9 May 2007, Johannes Schindelin wrote:
> > To be honest, I wouldn't even be *thinking* about the endianity of SHA-1
> > octet representation (you don't usually really deal with the hash as
> > with a number, so expecting to have it in native endianity is not very
> > natural; you just deal with it as with a data blob) and the
> > "(big-endian)" would only confuse me and get me thinking about "huh, do
> > they swap the bytes, or wait, they don't, ...?!".
> >
> > But that's maybe just me.
>
> But then, maybe it is just me? I got it completely wrong the first time,
> fully expecting the calculations to be carried out in host endianness for
> performance reasons.
I think the Mozilla implementation carries out calculations in host
endianness, and transfers data from the input to the internal state and
from the internal state to the final hash with shifts and masks.
Which calculations are you seeing that involve byte order?
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2007-05-09 16:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 15:10 [PATCH] Add a birdview-on-the-source-code section to the user manual Johannes Schindelin
2007-05-08 21:01 ` Karl Hasselström
2007-05-08 21:07 ` Johannes Schindelin
2007-05-08 21:31 ` Karl Hasselström
2007-05-08 23:10 ` Johannes Schindelin
2007-05-08 23:22 ` Karl Hasselström
2007-05-09 4:54 ` Daniel Barkalow
2007-05-09 6:31 ` Karl Hasselström
2007-05-09 9:38 ` Johannes Schindelin
2007-05-09 10:43 ` Karl Hasselström
2007-05-09 3:18 ` J. Bruce Fields
2007-05-09 4:06 ` Junio C Hamano
2007-05-09 5:05 ` Junio C Hamano
2007-05-09 9:33 ` Johannes Schindelin
2007-05-09 17:36 ` J. Bruce Fields
2007-05-09 6:48 ` Karl Hasselström
2007-05-09 9:27 ` Johannes Schindelin
2007-05-09 12:19 ` Johannes Schindelin
2007-05-09 12:32 ` Petr Baudis
2007-05-09 12:50 ` Johannes Schindelin
2007-05-09 16:18 ` Daniel Barkalow [this message]
2007-05-09 16:25 ` Johannes Schindelin
2007-05-09 17:07 ` J. Bruce Fields
2007-05-09 20:15 ` Johannes Schindelin
2007-05-09 20:32 ` J. Bruce Fields
2007-05-09 20:45 ` Daniel Barkalow
2007-05-09 22:23 ` Johannes Schindelin
2007-05-10 20:01 ` Karl Hasselström
2007-05-09 13:18 ` J. Bruce Fields
2007-05-10 4:15 ` Junio C Hamano
2007-05-10 10:36 ` Johannes Schindelin
2007-05-10 20:42 ` Junio C Hamano
2007-05-10 21:14 ` Karl Hasselström
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=Pine.LNX.4.64.0705091210570.18541@iabervon.org \
--to=barkalow@iabervon.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junio@cox.net \
--cc=kha@treskal.com \
--cc=pasky@suse.cz \
/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).