1git-name-rev(1) 2=============== 3 4NAME 5---- 6git-name-rev - Find symbolic names for given revs 7 8 9SYNOPSIS 10-------- 11[verse] 12'git name-rev' [--tags] [--refs=<pattern>] 13 ( --all | --stdin | <committish>... ) 14 15DESCRIPTION 16----------- 17Finds symbolic names suitable for human digestion for revisions given in any 18format parsable by 'git rev-parse'. 19 20 21OPTIONS 22------- 23 24--tags:: 25 Do not use branch names, but only tags to name the commits 26 27--refs=<pattern>:: 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. 30 31--all:: 32 List all commits reachable from all refs 33 34--stdin:: 35 Read from stdin, append "(<rev_name>)" to all sha1's of nameable 36 commits, and pass to stdout 37 38--name-only:: 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. 43 44--no-undefined:: 45 Die with error code != 0 when a reference is undefined, 46 instead of printing `undefined`. 47 48--always:: 49 Show uniquely abbreviated commit object as fallback. 50 51EXAMPLE 52------- 53 54Given a commit, find out where it is relative to the local refs. Say somebody 55wrote you about that fantastic commit 33db5f4d9027a10e477ccf054b2c1ab94f74c85a. 56Of course, you look into the commit, but that only tells you what happened, but 57not the context. 58 59Enter 'git name-rev': 60 61------------ 62% git name-rev 33db5f4d9027a10e477ccf054b2c1ab94f74c85a 6333db5f4d9027a10e477ccf054b2c1ab94f74c85a tags/v0.99~940 64------------ 65 66Now you are wiser, because you know that it happened 940 revisions before v0.99. 67 68Another nice thing you can do is: 69 70------------ 71% git log | git name-rev --stdin 72------------ 73 74GIT 75--- 76Part of the linkgit:git[1] suite