Junio C Hamano wrote: > "git name-rev" is supposed to convert 40-hex object names into > strings that name the same objects based on refs, that can be fed to > "git rev-parse" to get the same object names back, so > > $ git rev-parse v1.8.3 v1.8.3^0 | git name-rev --stdin > 8af06057d0c31a24e8737ae846ac2e116e8bafb9 > edca4152560522a431a51fc0a06147fc680b5b18 (tags/v1.8.3^0) Wait, what? $ git name-rev 8af060 8af060 tags/v1.8.3^0 Isn't this a failure specific to --stdin? > Teach it to show this instead: > > $ git rev-parse v1.8.3 v1.8.3^0 | git name-rev --stdin > 8af06057d0c31a24e8737ae846ac2e116e8bafb9 (tags/v1.8.3) > edca4152560522a431a51fc0a06147fc680b5b18 (tags/v1.8.3^0) Wait, what is name-rev? Finds symbolic names suitable for human digestion for revisions given in any format parsable by git rev-parse. It is meant to name _revisions_ (aka. commits): in that context, what sense does it make to distinguish between tags/v1.8.3 and tags/v1.8.3^0? -- 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