SYNOPSIS

git map [<extra_args>…]

DESCRIPTION

Git map formats the output of git log --graph from all refs such that:

  • Current branch is cyan.

  • Local branches are green.

  • Remote branches are red.

  • Tags are magenta.

  • Merge Base markers are white.

  • The currently checked out commit is highlighted with a blue background.

The output is automatically piped through the less pager command, even on windows.

OPTIONS

<extra_args>…

Extra parameters to pass to the internal git-log(1) invocation. This can be used to restrict what refs git map operates on, etc.

If you run git map with a series of fixed arguments frequently, you can use the depot-tools.map-extra configuration variable to pre-set arguments (See CONFIGURATION VARIABLES)

CONFIGURATION VARIABLES

depot-tools.map-extra

Each value of the depot-tools.map-extra config variable is applied as an additional argument to git log during the execution of git map. If you wish to configure this, use git config --add depot-tools.map-extra <value> to do so.

EXAMPLE

Running git map would result in an output something like: 

$ git map
* a8f0220	 (frozen_branch) 2014-04-10 ~ FREEZE.unindexed
* c382556	 2014-04-10 ~ modfile
* 06e399f	 2014-04-10 ~ a deleted file
* 20494d2	 (fixit) 2014-04-10 ~ Add neat feature    <(frozen_branch)
* f734bbf	 2014-04-10 ~ Epic README update
| * 983a7b8	 (cool_feature) 2014-04-10 ~ Respond to CL comments
| | * 2f53c1f	 (subfeature) 2014-04-10 ~ integrate with CoolService
| | * b4e5087	 2014-04-10 ~ slick commenting action
| |/
| * ac10591	 2014-04-10 ~ another improvement    <(subfeature)
| * 088691d	 (spleen_tag) 2014-04-10 ~ Refactor spleen
| * 206ceb2	 2014-04-10 ~ Add widget
|/
* 619ccc9	 (origin/master, origin/HEAD) 2014-04-10 ~ Make ReflectorImpl use mailboxes    <(cool_feature, fixit)
* 40b838e	 2014-04-10 ~ don't use glibc-specific execinfo.h on uclibc builds
* 65db351	 2014-04-10 ~ [fsp] Add requestUnmount() method together with the request manager.
* c1923e0	 2014-04-10 ~ linux_aura: Use system configuration for middle clicking the titlebar.
* ccaca03	 2014-04-10 ~ ContentView->ContentViewCore in ContentViewRenderView
* 9b1c1ab	 2014-04-10 ~ ozone: evdev: Filter devices by path
* a91bbf9	 2014-04-10 ~ Always output seccomp error messages to stderr

As you can see, the structure of the commit history is visible, particularly what the parents of each commit are. In order to see the upstream relationships of the branches (i.e. which branch is tracking which other branch), use the git-map-branches(1) command.

SEE ALSO

git-map-branches(1)

CHROMIUM DEPOT_TOOLS

Part of the chromium depot_tools(7) suite. These tools are meant to assist with the development of chromium and related projects. Download the tools from here.