Merge branch 'nd/warn-ambiguous-object-name' into next
commite87c9d1263354c671391e184ae89be5fe0af3d81
authorJunio C Hamano <gitster@pobox.com>
Tue, 4 Jun 2013 22:27:22 +0000 (4 15:27 -0700)
committerJunio C Hamano <gitster@pobox.com>
Tue, 4 Jun 2013 22:27:23 +0000 (4 15:27 -0700)
treec2537cfac75b0c1211f5e1e1e14abcfcfac05e1f
parent67d1fc7283096e46b6538a52d5dc0bafa708f642
parent798c35fcd8a71a094ca68ac05d81e08c5ac8166d
Merge branch 'nd/warn-ambiguous-object-name' into next

"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.

* nd/warn-ambiguous-object-name:
  get_sha1: warn about full or short object names that look like refs
advice.c
advice.h
sha1_name.c