"Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > Aneesh Kumar <aneesh.kumar@xxxxxxxxx> wrote: >> See i said that there should be a simple way. Can we get this >> documented in git-cat-file man page > > Well, this isn't the git-cat-file man page, but we do suggest people > use `git show HEAD:foo.c` to get foo.c from HEAD in an interactive > setting. The git-show manpage refers people to git-rev-parse, > which has the following: > > * A suffix ':' followed by a path; this names the blob or tree > at the given path in the tree-ish object named by the part > before the colon. > ... > But if you submit a documentation update to git-cat-file's manpage > that points off to the same section of git-rev-parse, folks may > appreciate it. :-) My feeling is that adding "See SPECIFYING REVISIONS section" to Porcelain documentation is a very good idea, but unwanted baggage for plumbing descriptions if added everywhere. The target audience of the latter is supposed to know what "object name" is, so: <object>:: - The sha1 identifier of the object. + The name of the object to show. should be sufficient. - 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