From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Barkalow 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) Message-ID: References: <20070509031803.GA27980@fieldses.org> <20070509123205.GN4489@pasky.or.cz> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Petr Baudis , "J. Bruce Fields" , kha@treskal.com, junio@cox.net, git@vger.kernel.org To: Johannes Schindelin X-From: git-owner@vger.kernel.org Wed May 09 18:19:02 2007 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1HlosW-00082o-Cl for gcvg-git@gmane.org; Wed, 09 May 2007 18:19:00 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754271AbXEIQSz (ORCPT ); Wed, 9 May 2007 12:18:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754393AbXEIQSz (ORCPT ); Wed, 9 May 2007 12:18:55 -0400 Received: from iabervon.org ([66.92.72.58]:3961 "EHLO iabervon.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754271AbXEIQSy (ORCPT ); Wed, 9 May 2007 12:18:54 -0400 Received: (qmail 25633 invoked by uid 1000); 9 May 2007 16:18:53 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 May 2007 16:18:53 -0000 In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: 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*