]> git.ipfire.org Git - thirdparty/git.git/blame - Documentation/git-name-rev.txt
Reuse fixup_pack_header_footer in index-pack
[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--------
2afc29aa
JS
11'git-name-rev' [--tags] [--refs=<pattern>]
12 ( --all | --stdin | <committish>... )
bd321bcc
JS
13
14DESCRIPTION
15-----------
16Finds symbolic names suitable for human digestion for revisions given in any
17format parsable by git-rev-parse.
18
19
20OPTIONS
21-------
22
23--tags::
24 Do not use branch names, but only tags to name the commits
25
2afc29aa
JS
26--refs=<pattern>::
27 Only use refs whose names match a given shell pattern.
28
bd321bcc
JS
29--all::
30 List all commits reachable from all refs
31
32--stdin::
82e5a82f 33 Read from stdin, append "(<rev_name>)" to all sha1's of nameable
bd321bcc
JS
34 commits, and pass to stdout
35
36EXAMPLE
37-------
38
39Given a commit, find out where it is relative to the local refs. Say somebody
2a75848e 40wrote you about that fantastic commit 33db5f4d9027a10e477ccf054b2c1ab94f74c85a.
bd321bcc
JS
41Of course, you look into the commit, but that only tells you what happened, but
42not the context.
43
44Enter git-name-rev:
45
46------------
47% git name-rev 33db5f4d9027a10e477ccf054b2c1ab94f74c85a
2b5f3ed3 4833db5f4d9027a10e477ccf054b2c1ab94f74c85a tags/v0.99^0~940
bd321bcc
JS
49------------
50
51Now you are wiser, because you know that it happened 940 revisions before v0.99.
52
53Another nice thing you can do is:
54
55------------
56% git log | git name-rev --stdin
57------------
58
59
60Author
61------
62Written by Johannes Schindelin <Johannes.Schindelin@gmx.de>
63
64Documentation
65--------------
66Documentation by Johannes Schindelin.
67
68GIT
69---
70Part of the gitlink:git[7] suite
71