Re: What's cooking in git.git (May 2013, #04; Wed, 15)

From: Duy Nguyen <pclouds@gmail.com>
Date: May 20, 2013, 10:18 UTC
Message-ID: <CACsJy8Cr7AKxo9sUjMCVQ0=O91L8CRoxD3qrvZczCrBUq4TDzA@mail.gmail.com>
In-Reply-To: <7vmwrvajye.fsf@alter.siamese.dyndns.org>

On Thu, May 16, 2013 at 6:42 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 12 quoted lines

> * nd/warn-ambiguous-object-name (2013-05-07) 1 commit
>  - get_sha1: improve ambiguity warning regarding SHA-1 and ref names
>
>  "git cmd <name>", when <name> happens to be a 40-hex string,
>  directly uses the 40-hex string as an object name, even if a ref
>  "refs/<some hierarchy>/<name>" exists.  This disambiguation order
>  is unlikely to change, but we should warn about the ambiguity just
>  like we warn when more than one refs/ hierachies share the same
>  name.
>
>  The message needs to be fixed up, as this is not "refname is
>  ambiguous".

hm.. how should the message be rephrased? ambiguity of 40-hex string and a ref path? -- Duy