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. 29 30--all:: 31 List all commits reachable from all refs 32 33--stdin:: 34 Read from stdin, append "(<rev_name>)" to all sha1's of nameable 35 commits, and pass to stdout 36 37--name-only:: 38 Instead of printing both the SHA-1 and the name, print only 39 the name. If given with --tags the usual tag prefix of 40 "tags/" is also omitted from the name, matching the output 41 of gitlink::git-describe[1] more closely. This option 42 cannot be combined with --stdin. 43 44EXAMPLE 45------- 46 47Given a commit, find out where it is relative to the local refs. Say somebody 48wrote you about that fantastic commit 33db5f4d9027a10e477ccf054b2c1ab94f74c85a. 49Of course, you look into the commit, but that only tells you what happened, but 50not the context. 51 52Enter git-name-rev: 53 54------------ 55% git name-rev 33db5f4d9027a10e477ccf054b2c1ab94f74c85a 5633db5f4d9027a10e477ccf054b2c1ab94f74c85a tags/v0.99^0~940 57------------ 58 59Now you are wiser, because you know that it happened 940 revisions before v0.99. 60 61Another nice thing you can do is: 62 63------------ 64% git log | git name-rev --stdin 65------------ 66 67 68Author 69------ 70Written by Johannes Schindelin <Johannes.Schindelin@gmx.de> 71 72Documentation 73-------------- 74Documentation by Johannes Schindelin. 75 76GIT 77--- 78Part of the gitlink:git[7] suite