Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756988Ab3D0CYa (ORCPT ); Fri, 26 Apr 2013 22:24:30 -0400 Received: from mail-ve0-f174.google.com ([209.85.128.174]:33068 "EHLO mail-ve0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752025Ab3D0CY2 (ORCPT ); Fri, 26 Apr 2013 22:24:28 -0400 MIME-Version: 1.0 In-Reply-To: <7vvc78u8jl.fsf@alter.siamese.dyndns.org> References: <7vvc78u8jl.fsf@alter.siamese.dyndns.org> From: shawn wilson Date: Fri, 26 Apr 2013 22:24:07 -0400 Message-ID: Subject: Re: [ANNOUNCE] Git v1.8.3-rc0 To: Junio C Hamano Cc: git@vger.kernel.org, Linux Kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 778 Lines: 16 On Fri, Apr 26, 2013 at 8:22 PM, Junio C Hamano wrote: > * There was no good way to ask "I have a random string that came from > outside world. I want to turn it into a 40-hex object name while > making sure such an object exists". A new peeling suffix ^{object} > can be used for that purpose, together with "rev-parse --verify". > What does this mean / what is the reason behind this? I can only think it might be useful in a test suite to make sure git isn't doing anything stupid with hashes...? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/