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