Manual Pages for Linux CentOS command on man git-show
MyWebUniversity

Manual Pages for Linux CentOS command on man git-show

GIT-SHOW(1) Git Manual GIT-SHOW(1)




NAME

       git-show - Show various types of objects

SYNOPSIS
       git show [options] ...


DESCRIPTION
       Shows one or more objects (blobs, trees, tags and commits).

       For commits it shows the log message and textual diff. It also presents

       the merge commit in a special format as produced by git diff-tree cc.

       For tags, it shows the tag message and the referenced objects.


       For trees, it shows the names (equivalent to git ls-tree with

       name-only).

       For plain blobs, it shows the plain contents.


       The command takes options applicable to the git diff-tree command to
       control how the changes the commit introduces are shown.

       This manual page describes only the most frequently used options.

OPTIONS
       ...
           The names of objects to show. For a more complete list of ways to
           spell object names, see "SPECIFYING REVISIONS" section in
           gitrevisions(7).

       pretty[=], format=

           Pretty-print the contents of the commit logs in a given format,
           where  can be one of oneline, short, medium, full, fuller,
           email, raw and format:. See the "PRETTY FORMATS" section
           for some additional details for each format. When omitted, the
           format defaults to medium.

           Note: you can specify the default pretty format in the repository

           configuration (see git-config(1)).


       abbrev-commit

           Instead of showing the full 40-byte hexadecimal commit object name,
           show only a partial prefix. Non default number of digits can be
           specified with "abbrev=" (which also modifies diff output, if
           it is displayed).

           This should make "pretty=oneline" a whole lot more readable for

           people using 80-column terminals.


       no-abbrev-commit

           Show the full 40-byte hexadecimal commit object name. This negates

           abbrev-commit and those options which imply it such as
           "oneline". It also overrides the log.abbrevCommit variable.

       oneline

           This is a shorthand for "pretty=oneline abbrev-commit" used
           together.

       encoding[=]
           The commit objects record the encoding used for the log message in
           their encoding header; this option can be used to tell the command

           to re-code the commit log message in the encoding preferred by the

           user. For non plumbing commands this defaults to UTF-8.

       notes[=]

           Show the notes (see git-notes(1)) that annotate the commit, when
           showing the commit log message. This is the default for git log,
           git show and git whatchanged commands when there is no pretty,
           format nor oneline option given on the command line.

           By default, the notes shown are from the notes refs listed in the
           core.notesRef and notes.displayRef variables (or corresponding

           environment overrides). See git-config(1) for more details.

           With an optional  argument, show this notes ref instead of the
           default notes ref(s). The ref is taken to be in refs/notes/ if it
           is not qualified.

           Multiple notes options can be combined to control which notes are
           being displayed. Examples: "notes=foo" will show only notes from
           "refs/notes/foo"; "notes=foo notes" will show both notes from
           "refs/notes/foo" and from the default notes ref(s).


       no-notes
           Do not show notes. This negates the above notes option, by
           resetting the list of notes refs from which notes are shown.
           Options are parsed in the order given on the command line, so e.g.

           "notes notes=foo no-notes notes=bar" will only show notes
           from "refs/notes/bar".


       show-notes[=], [no-]standard-notes

           These options are deprecated. Use the above notes/no-notes
           options instead.


       show-signature
           Check the validity of a signed commit object by passing the
           signature to gpg verify and show the output.

PRETTY FORMATS

       If the commit is a merge, and if the pretty-format is not oneline,
       email or raw, an additional line is inserted before the Author: line.
       This line begins with "Merge: " and the sha1s of ancestral commits are
       printed, separated by spaces. Note that the listed commits may not
       necessarily be the list of the direct parent commits if you have
       limited your view of history: for example, if you are only interested
       in changes related to a certain directory or file.


       There are several built-in formats, and you can define additional
       formats by setting a pretty. config option to either another

       format name, or a format: string, as described below (see git-

       config(1)). Here are the details of the built-in formats:

       ·   oneline

                

           This is designed to be as compact as possible.

       ·   short

               commit <sha1>
               Author: <author>

               <title line>

       ·   medium

               commit <sha1>
               Author: <author>
               Date:   <author date>

               <title line>

               <full commit message>

       ·   full

               commit <sha1>
               Author: <author>
               Commit: <committer>

               <title line>

               <full commit message>

       ·   fuller

               commit <sha1>
               Author:     <author>
               AuthorDate: <author date>
               Commit:     <committer>
               CommitDate: <committer date>

               <title line>

               <full commit message>

       ·   email

               From <sha1> <date>
               From: <author>
               Date: <author date>
               Subject: [PATCH] <title line>

               <full commit message>

       ·   raw

           The raw format shows the entire commit exactly as stored in the
<P>           commit object. Notably, the SHA-1s are displayed in full,
</P4><P>           regardless of whether abbrev or no-abbrev are used, and parents
</P4>           information show the true parent commits, without taking grafts nor
           history simplification into account.

       ·   format:<string>

           The format:<string> format allows you to specify which information
           you want to show. It works a little bit like printf format, with
<P>           the notable exception that you get a newline with %n instead of \n.
</P4>
<P>           E.g, format:"The author of %h was %an, %ar%nThe title was >>%s<<%n"
</P4>           would show something like this:

               The author of fe6e0ee was Junio C Hamano, 23 hours ago
<P>               The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<
</P4>
           The placeholders are:

<P>           ·   %H: commit hash
</P4>
<P>           ·   %h: abbreviated commit hash
</P4>
<P>           ·   %T: tree hash
</P4>
<P>           ·   %t: abbreviated tree hash
</P4>
<P>           ·   %P: parent hashes
</P4>
<P>           ·   %p: abbreviated parent hashes
</P4>
<P>           ·   %an: author name
</P4>
<P>           ·   %aN: author name (respecting .mailmap, see git-shortlog(1) or
</P4><P>               git-blame(1))
</P4>
<P>           ·   %ae: author email
</P4>
<P>           ·   %aE: author email (respecting .mailmap, see git-shortlog(1) or
</P4><P>               git-blame(1))
</P4>
<P>           ·   %ad: author date (format respects date= option)
</P4>
<P>           ·   %aD: author date, RFC2822 style
</P4>
<P>           ·   %ar: author date, relative
</P4>
<P>           ·   %at: author date, UNIX timestamp
</P4>
<P>           ·   %ai: author date, ISO 8601 format
</P4>
<P>           ·   %cn: committer name
</P4>
<P>           ·   %cN: committer name (respecting .mailmap, see git-shortlog(1)
</P4><P>               or git-blame(1))
</P4>
<P>           ·   %ce: committer email
</P4>
<P>           ·   %cE: committer email (respecting .mailmap, see git-shortlog(1)
</P4><P>               or git-blame(1))
</P4>
<P>           ·   %cd: committer date
</P4>
<P>           ·   %cD: committer date, RFC2822 style
</P4>
<P>           ·   %cr: committer date, relative
</P4>
<P>           ·   %ct: committer date, UNIX timestamp
</P4>
<P>           ·   %ci: committer date, ISO 8601 format
</P4>
<P>           ·   %d: ref names, like the decorate option of git-log(1)
</P4>
<P>           ·   %e: encoding
</P4>
<P>           ·   %s: subject
</P4>
<P>           ·   %f: sanitized subject line, suitable for a filename
</P4>
<P>           ·   %b: body
</P4>
<P>           ·   %B: raw body (unwrapped subject and body)
</P4>
<P>           ·   %N: commit notes
</P4>
<P>           ·   %GG: raw verification message from GPG for a signed commit
</P4>
<P>           ·   %G?: show "G" for a Good signature, "B" for a Bad signature,
</P4>               "U" for a good, untrusted signature and "N" for no signature

<P>           ·   %GS: show the name of the signer for a signed commit
</P4>
<P>           ·   %GK: show the key used to sign a signed commit
</P4>
<P>           ·   %gD: reflog selector, e.g., refs/stash@{1}
</P4>
<P>           ·   %gd: shortened reflog selector, e.g., stash@{1}
</P4>
<P>           ·   %gn: reflog identity name
</P4>
<P>           ·   %gN: reflog identity name (respecting .mailmap, see git-
</P4><P>               shortlog(1) or git-blame(1))
</P4>
<P>           ·   %ge: reflog identity email
</P4>
<P>           ·   %gE: reflog identity email (respecting .mailmap, see git-
</P4><P>               shortlog(1) or git-blame(1))
</P4>
<P>           ·   %gs: reflog subject
</P4>
<P>           ·   %Cred: switch color to red
</P4>
<P>           ·   %Cgreen: switch color to green
</P4>
<P>           ·   %Cblue: switch color to blue
</P4>
<P>           ·   %Creset: reset color
</P4>
<P>           ·   %C(...): color specification, as described in color.branch.*
</P4>               config option; adding auto, at the beginning will emit color
               only when colors are enabled for log output (by color.diff,
               color.ui, or color, and respecting the auto settings of the
               former if we are going to a terminal).  auto alone (i.e.
<P>               %C(auto)) will turn on auto coloring on the next placeholders
</P4>               until the color is switched again.

<P>           ·   %m: left, right or boundary mark
</P4>
<P>           ·   %n: newline
</P4>
<P>           ·   %%: a raw %
</P4>
<P>           ·   %x00: print a byte from a hex code
</P4>
<P>           ·   %w([<w>[,<i1>[,<i2>]]]): switch line wrapping, like the -w
</P4><P>               option of git-shortlog(1).
</P4>
<P>           ·   %<(<N>[,trunc|ltrunc|mtrunc]): make the next placeholder take
</P4>               at least N columns, padding spaces on the right if necessary.
               Optionally truncate at the beginning (ltrunc), the middle
               (mtrunc) or the end (trunc) if the output is longer than N
               columns. Note that truncating only works correctly with N >= 2.

<P>           ·   %<|(<N>): make the next placeholder take at least until Nth
</P4>               columns, padding spaces on the right if necessary

<P>           ·   %>(<N>), %>|(<N>): similar to %<(<N>), %<|(<N>) respectively,
</P4>               but padding spaces on the left

<P>           ·   %>>(<N>), %>>|(<N>): similar to %>(<N>), %>|(<N>) respectively,
</P4>               except that if the next placeholder takes more spaces than
               given and there are spaces on its left, use those spaces

<P>           ·   %><(<N>), %><|(<N>): similar to % <(<N>), %<|(<N>)
</P4>               respectively, but padding both sides (i.e. the text is
               centered)

           Note
           Some placeholders may depend on other options given to the revision
<P>           traversal engine. For example, the %g* reflog options will insert
</P4>           an empty string unless we are traversing reflog entries (e.g., by
<P>           git log -g). The %d placeholder will use the "short" decoration
</P4>           format if decorate was not already provided on the command line.

<P>       If you add a + (plus sign) after % of a placeholder, a line-feed is
</P4>       inserted immediately before the expansion if and only if the
<P>       placeholder expands to a non-empty string.
</P4>
<P>       If you add a - (minus sign) after % of a placeholder, line-feeds that
</P4>       immediately precede the expansion are deleted if and only if the
       placeholder expands to an empty string.

<P>       If you add a ` ` (space) after % of a placeholder, a space is inserted
</P4>       immediately before the expansion if and only if the placeholder expands
<P>       to a non-empty string.
</P4>
       ·   tformat:

           The tformat: format works exactly like format:, except that it
           provides "terminator" semantics instead of "separator" semantics.
           In other words, each commit has the message terminator character
           (usually a newline) appended, rather than a separator placed
<P>           between entries. This means that the final entry of a single-line
</P4>           format will be properly terminated with a new line, just as the
           "oneline" format does. For example:

<P>               $ git log -2 pretty=format:%h 4da45bef \
</P4><P>                 | perl -pe '$ .= "  NO NEWLINE\n" unless /\n/'
</P4>               4da45be
               7134973  NO NEWLINE

<P>               $ git log -2 pretty=tformat:%h 4da45bef \
</P4><P>                 | perl -pe '$ .= "  NO NEWLINE\n" unless /\n/'
</P4>               4da45be
               7134973

<P>           In addition, any unrecognized string that has a % in it is
</P4>           interpreted as if it has tformat: in front of it. For example,
           these two are equivalent:

<P>               $ git log -2 pretty=tformat:%h 4da45bef
</P4><P>               $ git log -2 pretty=%h 4da45bef
</P4>

EXAMPLES
       git show v1.0.0
           Shows the tag v1.0.0, along with the object the tags points at.

       git show v1.0.0^{tree}
           Shows the tree pointed to by the tag v1.0.0.

<P>       git show -s format=%s v1.0.0^{commit}
</P4>           Shows the subject of the commit pointed to by the tag v1.0.0.

       git show next~10:Documentation/README
           Shows the contents of the file Documentation/README as they were
           current in the 10th last commit of the branch next.

       git show master:Makefile master:t/Makefile
           Concatenates the contents of said Makefiles in the head of the
           branch master.

DISCUSSION
       At the core level, Git is character encoding agnostic.

       ·   The pathnames recorded in the index and in the tree objects are
<P>           treated as uninterpreted sequences of non-NUL bytes. What
</P4>           readdir(2) returns are what are recorded and compared with the data
           Git keeps track of, which in turn are expected to be what lstat(2)
           and creat(2) accepts. There is no such thing as pathname encoding
           translation.

       ·   The contents of the blob objects are uninterpreted sequences of
           bytes. There is no encoding translation at the core level.

<P>       ·   The commit log messages are uninterpreted sequences of non-NUL
</P4>           bytes.

       Although we encourage that the commit log messages are encoded in
<P>       UTF-8, both the core and Git Porcelain are designed not to force UTF-8
</P4>       on projects. If all participants of a particular project find it more
       convenient to use legacy encodings, Git does not forbid it. However,
       there are a few things to keep in mind.

<P>        1. git commit and git commit-tree issues a warning if the commit log
</P4><P>           message given to it does not look like a valid UTF-8 string, unless
</P4>           you explicitly say your project uses a legacy encoding. The way to
           say this is to have i18n.commitencoding in .git/config file, like
           this:

               [i18n]
<P>                       commitencoding = ISO-8859-1
</P4>
           Commit objects created with the above setting record the value of
           i18n.commitencoding in its encoding header. This is to help other
           people who look at them later. Lack of this header implies that the
<P>           commit log message is encoded in UTF-8.
</P4>
        2. git log, git show, git blame and friends look at the encoding
<P>           header of a commit object, and try to re-code the log message into
</P4><P>           UTF-8 unless otherwise specified. You can specify the desired
</P4>           output encoding with i18n.logoutputencoding in .git/config file,
           like this:

               [i18n]
<P>                       logoutputencoding = ISO-8859-1
</P4>
           If you do not have this configuration variable, the value of
           i18n.commitencoding is used instead.

<P>       Note that we deliberately chose not to re-code the commit log message
</P4><P>       when a commit is made to force UTF-8 at the commit object level,
</P4><P>       because re-coding to UTF-8 is not necessarily a reversible operation.
</P4>
GIT
       Part of the git(1) suite



<P>Git 1.8.3.1                       11/02/2018                       GIT-SHOW(1)
</P4></P></pre></div><br></div><br><BR>
<center>
<a target="_top" href="https://www.mywebuniversity.com/contact.html">
<font size=-1 color=WHITE><B>Contact us<B></font></a>     
<font size=-1 color=WHITE>|</font>     
<a target="_top" href="https://www.mywebuniversity.com/contact.html">
<B><font size=-1 color=WHITE>About us</font></B></a>
     <font size=-1 color=WHITE>|</font>     
<a target="_top" href="https://www.mywebuniversity.com/contact.html"><font size=-1 color=WHITE>Term of use</font></a>
     <font size=-1 color=WHITE>| </font>     <font size=-1 color=WHITE>
<b>Copyright  © 2000-2019 MyWebUniversity.com ™</b></font>
</center>

</body>
</html>