On Tue, Jun 7, 2016 at 3:29 PM, Jeff King <peff@xxxxxxxx> wrote: > or even: > > git tag --show-tag-name foo/v1.0 > > when refs/remotes/foo/v1.0 exists? > > The rule right now is generally that "git tag" takes actual tag names. Ahh, I forgot about that. Yes, indeed the command does not work like other Git commands, which would just let generic revision parser to accept an object name from anywhere. Probably it was a mistake, because "git tag --verify $T" may find refs/tags/$T but that may not necessarily mean "git checkout $T^0" would give you that exact tree state, but it is too late to change now. So yes, I agree with you that any validation-related thing needs to start from names relative to refs/tags/, not from object names, to be consistent. Which is a bit sad, but I do not offhand think of a way to avoid it. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html