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.
31 List all commits reachable from all refs
34 Transform stdin by substituting all the 40-character SHA-1
35 hexes (say $hex) with "$hex ($rev_name)". When used with
36 --name-only, substitute with "$rev_name", omitting $hex
37 altogether. Intended for the scripter's use.
40 Instead of printing both the SHA-1 and the name, print only
41 the name. If given with --tags the usual tag prefix of
42 "tags/" is also omitted from the name, matching the output
43 of `git-describe` more closely.
46 Die with error code != 0 when a reference is undefined,
47 instead of printing `undefined`.
50 Show uniquely abbreviated commit object as fallback.
55 Given a commit, find out where it is relative to the local refs. Say somebody
56 wrote you about that fantastic commit 33db5f4d9027a10e477ccf054b2c1ab94f74c85a.
57 Of course, you look into the commit, but that only tells you what happened, but
63 % git name-rev 33db5f4d9027a10e477ccf054b2c1ab94f74c85a
64 33db5f4d9027a10e477ccf054b2c1ab94f74c85a tags/v0.99~940
67 Now you are wiser, because you know that it happened 940 revisions before v0.99.
69 Another nice thing you can do is:
72 % git log | git name-rev --stdin
77 Part of the linkgit:git[1] suite