Documentation / git-log.txton commit Merge branch 'ph/parseopt' (c9618ff)
   1git-log(1)
   2==========
   3
   4NAME
   5----
   6git-log - Show commit logs
   7
   8
   9SYNOPSIS
  10--------
  11'git log' [<options>] [<since>..<until>] [[\--] <path>...]
  12
  13DESCRIPTION
  14-----------
  15Shows the commit logs.
  16
  17The command takes options applicable to the 'git-rev-list'
  18command to control what is shown and how, and options applicable to
  19the 'git-diff-*' commands to control how the changes
  20each commit introduces are shown.
  21
  22
  23OPTIONS
  24-------
  25
  26:git-log: 1
  27include::diff-options.txt[]
  28
  29-<n>::
  30        Limits the number of commits to show.
  31
  32<since>..<until>::
  33        Show only commits between the named two commits.  When
  34        either <since> or <until> is omitted, it defaults to
  35        `HEAD`, i.e. the tip of the current branch.
  36        For a more complete list of ways to spell <since>
  37        and <until>, see "SPECIFYING REVISIONS" section in
  38        linkgit:git-rev-parse[1].
  39
  40--decorate::
  41        Print out the ref names of any commits that are shown.
  42
  43--full-diff::
  44        Without this flag, "git log -p <path>..." shows commits that
  45        touch the specified paths, and diffs about the same specified
  46        paths.  With this, the full diff is shown for commits that touch
  47        the specified paths; this means that "<path>..." limits only
  48        commits, and doesn't limit diff for those commits.
  49
  50--follow::
  51        Continue listing the history of a file beyond renames.
  52
  53--log-size::
  54        Before the log message print out its size in bytes. Intended
  55        mainly for porcelain tools consumption. If git is unable to
  56        produce a valid value size is set to zero.
  57        Note that only message is considered, if also a diff is shown
  58        its size is not included.
  59
  60[\--] <path>...::
  61        Show only commits that affect any of the specified paths. To
  62        prevent confusion with options and branch names, paths may need
  63        to be prefixed with "\-- " to separate them from options or
  64        refnames.
  65
  66
  67include::rev-list-options.txt[]
  68
  69include::pretty-formats.txt[]
  70
  71include::diff-generate-patch.txt[]
  72
  73Examples
  74--------
  75git log --no-merges::
  76
  77        Show the whole commit history, but skip any merges
  78
  79git log v2.6.12.. include/scsi drivers/scsi::
  80
  81        Show all commits since version 'v2.6.12' that changed any file
  82        in the include/scsi or drivers/scsi subdirectories
  83
  84git log --since="2 weeks ago" \-- gitk::
  85
  86        Show the changes during the last two weeks to the file 'gitk'.
  87        The "--" is necessary to avoid confusion with the *branch* named
  88        'gitk'
  89
  90git log --name-status release..test::
  91
  92        Show the commits that are in the "test" branch but not yet
  93        in the "release" branch, along with the list of paths
  94        each commit modifies.
  95
  96git log --follow builtin-rev-list.c::
  97
  98        Shows the commits that changed builtin-rev-list.c, including
  99        those commits that occurred before the file was given its
 100        present name.
 101
 102Discussion
 103----------
 104
 105include::i18n.txt[]
 106
 107
 108Author
 109------
 110Written by Linus Torvalds <torvalds@osdl.org>
 111
 112Documentation
 113--------------
 114Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
 115
 116GIT
 117---
 118Part of the linkgit:git[1] suite