From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Abrahams Subject: Re: [doc] User Manual Suggestion Date: Fri, 24 Apr 2009 20:41:12 -0400 Message-ID: References: <200904240051.46233.johan@herland.net> <200904242230.13239.johan@herland.net> <20090424213848.GA14493@coredump.intra.peff.net> Mime-Version: 1.0 (Apple Message framework v930.4) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Cc: Michael Witten , Jeff King , Johan Herland , git@vger.kernel.org, "J. Bruce Fields" To: Daniel Barkalow X-From: git-owner@vger.kernel.org Sat Apr 25 02:42:50 2009 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1LxVyi-00082J-PX for gcvg-git-2@gmane.org; Sat, 25 Apr 2009 02:42:49 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752211AbZDYAlP (ORCPT ); Fri, 24 Apr 2009 20:41:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751437AbZDYAlP (ORCPT ); Fri, 24 Apr 2009 20:41:15 -0400 Received: from boost-consulting.com ([206.71.190.141]:64999 "EHLO boost-consulting.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751301AbZDYAlP (ORCPT ); Fri, 24 Apr 2009 20:41:15 -0400 Received: from [192.168.188.150] (207-172-223-249.c3-0.smr-ubr3.sbo-smr.ma.static.cable.rcn.com [207.172.223.249]) (Authenticated sender: dave) by boost-consulting.com (Postfix) with ESMTPSA id 4F0E31CC23; Fri, 24 Apr 2009 17:38:43 -0700 (PDT) In-Reply-To: X-Mailer: Apple Mail (2.930.4) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Apr 24, 2009, at 7:11 PM, Daniel Barkalow wrote: > I actually think calling them "sha1s" is better, simply because this > bit > of jargon doesn't mean anything else (git deals with email, so > "address" > is overloaded). And the term is already in use for this particular > case, > and it doesn't mean anything else at all (since, of course, the crypto > thing is "SHA-1", not "sha1"), and it's short (which is important for > making it easy to look at usage help). The word "hash" would be an improvement. -- David Abrahams BoostPro Computing http://boostpro.com