Documentation / git-whatchanged.txton commit test-lib.sh: Add new function, test_expect_code (d3bfdb7)
   1git-whatchanged(1)
   2==================
   3
   4NAME
   5----
   6git-whatchanged - Show logs with difference each commit introduces.
   7
   8
   9SYNOPSIS
  10--------
  11'git-whatchanged' <option>...
  12
  13DESCRIPTION
  14-----------
  15Shows commit logs and diff output each commit introduces.  The
  16command internally invokes 'git-rev-list' piped to
  17'git-diff-tree', and takes command line options for both of
  18these commands.
  19
  20This manual page describes only the most frequently used options.
  21
  22
  23OPTIONS
  24-------
  25-p::
  26        Show textual diffs, instead of the git internal diff
  27        output format that is useful only to tell the changed
  28        paths and their nature of changes.
  29
  30--max-count=<n>::
  31        Limit output to <n> commits.
  32
  33<since>..<until>::
  34        Limit output to between the two named commits (bottom
  35        exclusive, top inclusive).
  36
  37-r::
  38        Show git internal diff output, but for the whole tree,
  39        not just the top level.
  40
  41--pretty=<format>::
  42        Controls the output format for the commit logs.
  43        <format> can be one of 'raw', 'medium', 'short', 'full',
  44        and 'oneline'.
  45
  46-m::
  47        By default, differences for merge commits are not shown.
  48        With this flag, show differences to that commit from all
  49        of its parents.
  50
  51        However, it is not very useful in general, although it
  52        *is* useful on a file-by-file basis.
  53
  54Examples
  55--------
  56git-whatchanged -p v2.6.12.. include/scsi drivers/scsi::
  57
  58        Show as patches the commits since version 'v2.6.12' that changed
  59        any file in the include/scsi or drivers/scsi subdirectories
  60
  61git-whatchanged --since="2 weeks ago" -- gitk::
  62
  63        Show the changes during the last two weeks to the file 'gitk'.
  64        The "--" is necessary to avoid confusion with the *branch* named
  65        'gitk'
  66
  67
  68Author
  69------
  70Written by Linus Torvalds <torvalds@osdl.org> and
  71Junio C Hamano <junkio@cox.net>
  72
  73
  74Documentation
  75--------------
  76Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
  77
  78GIT
  79---
  80Part of the gitlink:git[7] suite
  81