- bookworm 1:2.39.2-1.1
- testing 1:2.45.2-1
- unstable 1:2.45.2-1.2
- experimental 1:2.45.2+next.20240614-1
GIT-NAME-REV(1) | Git Manual | GIT-NAME-REV(1) |
NAME¶
git-name-rev - Find symbolic names for given revs
SYNOPSIS¶
git name-rev [--tags] [--refs=<pattern>]
( --all | --stdin | <commit-ish>... )
DESCRIPTION¶
Finds symbolic names suitable for human digestion for revisions given in any format parsable by git rev-parse.
OPTIONS¶
--tags
--refs=<pattern>
--exclude=<pattern>
--all
--annotate-stdin
For example:
$ cat sample.txt An abbreviated revision 2ae0a9cb82 will not be substituted. The full name after substitution is 2ae0a9cb8298185a94e5998086f380a355dd8907, while its tree object is 70d105cc79e63b81cfdcb08a15297c23e60b07ad $ git name-rev --annotate-stdin <sample.txt An abbreviated revision 2ae0a9cb82 will not be substituted. The full name after substitution is 2ae0a9cb8298185a94e5998086f380a355dd8907 (master), while its tree object is 70d105cc79e63b81cfdcb08a15297c23e60b07ad $ git name-rev --name-only --annotate-stdin <sample.txt An abbreviated revision 2ae0a9cb82 will not be substituted. The full name after substitution is master, while its tree object is 70d105cc79e63b81cfdcb08a15297c23e60b07ad
--stdin
--name-only
--no-undefined
--always
EXAMPLES¶
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~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
GIT¶
Part of the git(1) suite
02/28/2023 | Git 2.39.2 |