6 git-name-rev - Find symbolic names for given revs
12 'git name-rev' [--tags] [--refs=<pattern>]
13 ( --all | --stdin | <committish>... )
17 Finds symbolic names suitable for human digestion for revisions given in any
18 format parsable by 'git rev-parse'.
25 Do not use branch names, but only tags to name the commits
28 Only use refs whose names match a given shell pattern. The pattern
29 can be one of branch name, tag name or fully qualified ref name.
32 List all commits reachable from all refs
35 Read from stdin, append "(<rev_name>)" to all sha1's of nameable
36 commits, and pass to stdout
39 Instead of printing both the SHA-1 and the name, print only
40 the name. If given with --tags the usual tag prefix of
41 "tags/" is also omitted from the name, matching the output
42 of `git-describe` more closely.
45 Die with error code != 0 when a reference is undefined,
46 instead of printing `undefined`.
49 Show uniquely abbreviated commit object as fallback.
54 Given a commit, find out where it is relative to the local refs. Say somebody
55 wrote you about that fantastic commit 33db5f4d9027a10e477ccf054b2c1ab94f74c85a.
56 Of course, you look into the commit, but that only tells you what happened, but
62 % git name-rev 33db5f4d9027a10e477ccf054b2c1ab94f74c85a
63 33db5f4d9027a10e477ccf054b2c1ab94f74c85a tags/v0.99~940
66 Now you are wiser, because you know that it happened 940 revisions before v0.99.
68 Another nice thing you can do is:
71 % git log | git name-rev --stdin
76 Part of the linkgit:git[1] suite