summaryrefslogtreecommitdiff
path: root/Documentation/git-name-rev.txt
blob: 37fbf66efb91ff74bf57d1b33b5ab95a248713cd (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
git-name-rev(1)
===============
 
NAME
----
git-name-rev - Find symbolic names for given revs
 
 
SYNOPSIS
--------
'git-name-rev' [--tags] ( --all | --stdin | <committish>... )
 
DESCRIPTION
-----------
Finds symbolic names suitable for human digestion for revisions given in any
format parsable by git-rev-parse.
 
 
OPTIONS
-------
 
--tags::
	Do not use branch names, but only tags to name the commits
 
--all::
	List all commits reachable from all refs
 
--stdin::
	Read from stdin, append "(<rev_name>)" to all sha1's of nameable
	commits, and pass to stdout
 
EXAMPLE
-------
 
Given a commit, find out where it is relative to the local refs. Say somebody
wrote you about that fantastic commit 33db5f4d9027a10e477ccf054b2c1ab94f74c85a.
Of course, you look into the commit, but that only tells you what happened, but
not the context.
 
Enter git-name-rev:
 
------------
% git name-rev 33db5f4d9027a10e477ccf054b2c1ab94f74c85a
33db5f4d9027a10e477ccf054b2c1ab94f74c85a tags/v0.99^0~940
------------
 
Now you are wiser, because you know that it happened 940 revisions before v0.99.
 
Another nice thing you can do is:
 
------------
% git log | git name-rev --stdin
------------
 
 
Author
------
Written by Johannes Schindelin <Johannes.Schindelin@gmx.de>
 
Documentation
--------------
Documentation by Johannes Schindelin.
 
GIT
---
Part of the gitlink:git[7] suite