зеркало из https://github.com/microsoft/git.git
67 строки
1.3 KiB
Plaintext
67 строки
1.3 KiB
Plaintext
git-name-rev(1)
|
|
===============
|
|
|
|
NAME
|
|
----
|
|
git-name-rev - Find symbolic names for given revs.
|
|
|
|
|
|
SYNOPSIS
|
|
--------
|
|
'git-name-rev' [--tags] ( --all | --stdin | <commitish>... )
|
|
|
|
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 name'able
|
|
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 phantastic 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
|
|
------------
|
|
|
|
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
|
|
|