git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
	Petr Baudis <pasky@suse.cz>,
	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 13:07:25 -0400	[thread overview]
Message-ID: <20070509170725.GB23778@fieldses.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705091822590.4167@racer.site>

On Wed, May 09, 2007 at 06:25:01PM +0200, Johannes Schindelin wrote:
> None. I only suspected them to be carried out in byte order. From what I 
> know, there are some shifts involved, which might or might not be helped 
> by 32-bit arithmetic.
> 
> I did not really look into it.
> 
> From my prior debugging experiences on Intel, though, I automatically 
> looked for the least significant bytes at the beginning of those "sha1" 
> variables, and came up empty.

So, I'm confused about what you actually mean by "big endian" here.  I
originally assumed that you meant that SHA1's are defined as bit arrays,
and that the first bit of the SHA1 is in the high-order bit of the first
byte.  But if you just meant that the first byte of the SHA1 is stored
in the first byte of the array...  that kind of goes without saying,
doesn't it?

In any case, maybe this is a detail that's best left to the code itself.

--b.

  reply	other threads:[~2007-05-09 17:07 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
2007-05-09 16:25           ` Johannes Schindelin
2007-05-09 17:07             ` J. Bruce Fields [this message]
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=20070509170725.GB23778@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=barkalow@iabervon.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).