Go to main content

man pages section 1: User Commands

Exit Print View

Updated: July 2017
 
 

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

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
           Do not use branch names, but only tags to name the commits

       --refs=<pattern>
           Only use refs whose names match a given shell pattern. The pattern
           can be one of branch name, tag name or fully qualified ref name.

       --all
           List all commits reachable from all refs

       --stdin
           Transform stdin by substituting all the 40-character SHA-1 hexes
           (say $hex) with "$hex ($rev_name)". When used with --name-only,
           substitute with "$rev_name", omitting $hex altogether. Intended for
           the scripter's use.

       --name-only
           Instead of printing both the SHA-1 and the name, print only the
           name. If given with --tags the usual tag prefix of "tags/" is also
           omitted from the name, matching the output of git-describe more
           closely.

       --no-undefined
           Die with error code != 0 when a reference is undefined, instead of
           printing undefined.

       --always
           Show uniquely abbreviated commit object as fallback.

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~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



ATTRIBUTES
       See attributes(5) for descriptions of the following attributes:


       +---------------+--------------------------+
       |ATTRIBUTE TYPE |     ATTRIBUTE VALUE      |
       +---------------+--------------------------+
       |Availability   | developer/versioning/git |
       +---------------+--------------------------+
       |Stability      | Uncommitted              |
       +---------------+--------------------------+
NOTES
       This software was built from source available at
       https://java.net/projects/solaris-userland.  The original community
       source was downloaded from
       https://www.kernel.org/pub/software/scm/git/git-2.7.4.tar.xz

       Further information about this software can be found on the open source
       community website at http://git-scm.com/.



Git 2.7.4                         03/17/2016                   GIT-NAME-REV(1)