There seems to be an inconsistency between the fetch and tag over whether lightweight tags of non-commits are allowed. Fetch doesn't like them, but tag creates them without any particular fuss. I think that fetch is right that, if you want to tag a blob, you should use a real tag object so that there's something that indicates (correctly) the type of the tagged object. Should git-tag perhaps automatically make a tag object if the tagged object isn't a commit, acting as if -a was given, except that an empty message is used instead of invoking an editor if -m is not given? (I can, of course, just use git-tag that way, but it seems generally unfriendly to by able to get "error:" out of a sequence of purely git commands, even if they're sort of odd and probably not what you really wanted to do. -Daniel *This .sig left intentionally blank* - 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
