From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: [PATCH] Add a birdview-on-the-source-code section to the user manual Date: Wed, 9 May 2007 16:32:09 -0400 Message-ID: <20070509203209.GM23778@fieldses.org> References: <20070509031803.GA27980@fieldses.org> <20070509123205.GN4489@pasky.or.cz> <20070509170725.GB23778@fieldses.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Daniel Barkalow , Petr Baudis , kha@treskal.com, junio@cox.net, git@vger.kernel.org To: Johannes Schindelin X-From: git-owner@vger.kernel.org Wed May 09 22:32:28 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 1Hlspm-0000LC-IZ for gcvg-git@gmane.org; Wed, 09 May 2007 22:32:26 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753329AbXEIUcW (ORCPT ); Wed, 9 May 2007 16:32:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753376AbXEIUcW (ORCPT ); Wed, 9 May 2007 16:32:22 -0400 Received: from mail.fieldses.org ([66.93.2.214]:55145 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753329AbXEIUcV (ORCPT ); Wed, 9 May 2007 16:32:21 -0400 Received: from bfields by fieldses.org with local (Exim 4.67) (envelope-from ) id 1HlspV-0002p2-O8; Wed, 09 May 2007 16:32:09 -0400 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: On Wed, May 09, 2007 at 10:15:19PM +0200, Johannes Schindelin wrote: > If you parse a number, passed to a program, with strtol(argv[1], NULL, 0) > you would expect something like this on an Intel processor: > > Input 0x1234 -> memory 0x34 0x12 0x00 0x00. Right, but this is something special to integers. If it made sense for some strange reason to define the structure carrying a sha1 as int[5] instead of char[20] then I'd understand the confusion, but char[20] is totally unambiguous. > But if all this sounds too confusing, I agree to delete the > "(big-endian)". Yeah, I think that'd be best; thanks. --b.