git-show-branch - Show branches and their commits


   git show-branch [-a|--all] [-r|--remotes] [--topo-order | --date-order]
                   [--current] [--color[=<when>] | --no-color] [--sparse]
                   [--more=<n> | --list | --independent | --merge-base]
                   [--no-name | --sha1-name] [--topics]
                   [(<rev> | <glob>)...]
   git show-branch (-g|--reflog)[=<n>[,<base>]] [--list] [<ref>]


   Shows the commit ancestry graph starting from the commits named with
   <rev>s or <globs>s (or all refs under refs/heads and/or refs/tags)

   It cannot show more than 29 branches and commits at a time.

   It uses showbranch.default multi-valued configuration items if no <rev>
   or <glob> is given on the command line.


       Arbitrary extended SHA-1 expression (see gitrevisions(7)) that
       typically names a branch head or a tag.

       A glob pattern that matches branch or tag names under refs/. For
       example, if you have many topic branches under refs/heads/topic,
       giving topic/* would show all of them.

   -r, --remotes
       Show the remote-tracking branches.

   -a, --all
       Show both remote-tracking branches and local branches.

       With this option, the command includes the current branch to the
       list of revs to be shown when it is not given on the command line.

       By default, the branches and their commits are shown in reverse
       chronological order. This option makes them appear in topological
       order (i.e., descendant commits are shown before their parents).

       This option is similar to --topo-order in the sense that no parent
       comes before all of its children, but otherwise commits are ordered
       according to their commit date.

       By default, the output omits merges that are reachable from only
       one tip being shown. This option makes them visible.

       Usually the command stops output upon showing the commit that is
       the common ancestor of all the branches. This flag tells the
       command to go <n> more common commits beyond that. When <n> is
       negative, display only the <reference>s given, without showing the
       commit ancestry tree.

       Synonym to --more=-1

       Instead of showing the commit list, determine possible merge bases
       for the specified commits. All merge bases will be contained in all
       specified commits. This is different from how git-merge-base(1)
       handles the case of three or more commits.

       Among the <reference>s given, display only the ones that cannot be
       reached from any other <reference>.

       Do not show naming strings for each commit.

       Instead of naming the commits using the path to reach them from
       heads (e.g. "master~2" to mean the grandparent of "master"), name
       them with the unique prefix of their object names.

       Shows only commits that are NOT on the first branch given. This
       helps track topic branches by hiding any commit that is already in
       the main line of development. When given "git show-branch --topics
       master topic1 topic2", this will show the revisions given by "git
       rev-list ^master topic1 topic2"

   -g, --reflog[=<n>[,<base>]] [<ref>]
       Shows <n> most recent ref-log entries for the given ref. If <base>
       is given, <n> entries going back from that entry. <base> can be
       specified as count or date. When no explicit <ref> parameter is
       given, it defaults to the current branch (or HEAD if it is

       Color the status sign (one of these: * !  + -) of each commit
       corresponding to the branch it's in. The value must be always (the
       default), never, or auto.

       Turn off colored output, even when the configuration file gives the
       default to color output. Same as --color=never.

   Note that --more, --list, --independent and --merge-base options are
   mutually exclusive.


   Given N <references>, the first N lines are the one-line description
   from their commit message. The branch head that is pointed at by
   $GIT_DIR/HEAD is prefixed with an asterisk * character while other
   heads are prefixed with a ! character.

   Following these N lines, one-line log for each commit is displayed,
   indented N places. If a commit is on the I-th branch, the I-th
   indentation character shows a + sign; otherwise it shows a space. Merge
   commits are denoted by a - sign. Each commit shows a short name that
   can be used as an extended SHA-1 to name that commit.

   The following example shows three branches, "master", "fixes" and

       $ git show-branch master fixes mhf
       * [master] Add 'git show-branch'.
        ! [fixes] Introduce "reset type" flag to "git reset"
         ! [mhf] Allow "+remote:local" refspec to cause --force when fetching.
         + [mhf] Allow "+remote:local" refspec to cause --force when fetching.
         + [mhf~1] Use git-octopus when pulling more than one heads.
        +  [fixes] Introduce "reset type" flag to "git reset"
         + [mhf~2] "git fetch --force".
         + [mhf~3] Use .git/remote/origin, not .git/branches/origin.
         + [mhf~4] Make "git pull" and "git fetch" default to origin
         + [mhf~5] Infamous 'octopus merge'
         + [mhf~6] Retire git-parse-remote.
         + [mhf~7] Multi-head fetch.
         + [mhf~8] Start adding the $GIT_DIR/remotes/ support.
       *++ [master] Add 'git show-branch'.

   These three branches all forked from a common commit, [master], whose
   commit message is "Add 'git show-branch'". The "fixes" branch adds one
   commit "Introduce "reset type" flag to "git reset"". The "mhf" branch
   adds many other commits. The current branch is "master".


   If you keep your primary branches immediately under refs/heads, and
   topic branches in subdirectories of it, having the following in the
   configuration file may help:

               default = --topo-order
               default = heads/*

   With this, git show-branch without extra parameters would show only the
   primary branches. In addition, if you happen to be on your topic
   branch, it is shown as well.

       $ git show-branch --reflog="10,1 hour ago" --list master

   shows 10 reflog entries going back from the tip as of 1 hour ago.
   Without --list, the output also shows how these tips are topologically
   related with each other.


   Part of the git(1) suite


Personal Opportunity - Free software gives you access to billions of dollars of software at no cost. Use this software for your business, personal use or to develop a profitable skill. Access to source code provides access to a level of capabilities/information that companies protect though copyrights. Open source is a core component of the Internet and it is available to you. Leverage the billions of dollars in resources and capabilities to build a career, establish a business or change the world. The potential is endless for those who understand the opportunity.

Business Opportunity - Goldman Sachs, IBM and countless large corporations are leveraging open source to reduce costs, develop products and increase their bottom lines. Learn what these companies know about open source and how open source can give you the advantage.

Free Software

Free Software provides computer programs and capabilities at no cost but more importantly, it provides the freedom to run, edit, contribute to, and share the software. The importance of free software is a matter of access, not price. Software at no cost is a benefit but ownership rights to the software and source code is far more significant.

Free Office Software - The Libre Office suite provides top desktop productivity tools for free. This includes, a word processor, spreadsheet, presentation engine, drawing and flowcharting, database and math applications. Libre Office is available for Linux or Windows.

Free Books

The Free Books Library is a collection of thousands of the most popular public domain books in an online readable format. The collection includes great classical literature and more recent works where the U.S. copyright has expired. These books are yours to read and use without restrictions.

Source Code - Want to change a program or know how it works? Open Source provides the source code for its programs so that anyone can use, modify or learn how to write those programs themselves. Visit the GNU source code repositories to download the source.


Study at Harvard, Stanford or MIT - Open edX provides free online courses from Harvard, MIT, Columbia, UC Berkeley and other top Universities. Hundreds of courses for almost all major subjects and course levels. Open edx also offers some paid courses and selected certifications.

Linux Manual Pages - A man or manual page is a form of software documentation found on Linux/Unix operating systems. Topics covered include computer programs (including library and system calls), formal standards and conventions, and even abstract concepts.