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--no-decorate:: 41--decorate[=short|full|no]:: 42 Print out the ref names of any commits that are shown. If 'short' is 43 specified, the ref name prefixes 'refs/heads/', 'refs/tags/' and 44 'refs/remotes/' will not be printed. If 'full' is specified, the 45 full ref name (including prefix) will be printed. The default option 46 is 'short'. 47 48--source:: 49 Print out the ref name given on the command line by which each 50 commit was reached. 51 52--full-diff:: 53 Without this flag, "git log -p <path>..." shows commits that 54 touch the specified paths, and diffs about the same specified 55 paths. With this, the full diff is shown for commits that touch 56 the specified paths; this means that "<path>..." limits only 57 commits, and doesn't limit diff for those commits. 58 59--follow:: 60 Continue listing the history of a file beyond renames/copies. 61 62--log-size:: 63 Before the log message print out its size in bytes. Intended 64 mainly for porcelain tools consumption. If git is unable to 65 produce a valid value size is set to zero. 66 Note that only message is considered, if also a diff is shown 67 its size is not included. 68 69[\--] <path>...:: 70 Show only commits that affect any of the specified paths. To 71 prevent confusion with options and branch names, paths may need 72 to be prefixed with "\-- " to separate them from options or 73 refnames. 74 75 76include::rev-list-options.txt[] 77 78include::pretty-formats.txt[] 79 80include::diff-generate-patch.txt[] 81 82Examples 83-------- 84git log --no-merges:: 85 86 Show the whole commit history, but skip any merges 87 88git log v2.6.12.. include/scsi drivers/scsi:: 89 90 Show all commits since version 'v2.6.12' that changed any file 91 in the include/scsi or drivers/scsi subdirectories 92 93git log --since="2 weeks ago" \-- gitk:: 94 95 Show the changes during the last two weeks to the file 'gitk'. 96 The "--" is necessary to avoid confusion with the *branch* named 97 'gitk' 98 99git log --name-status release..test:: 100 101 Show the commits that are in the "test" branch but not yet 102 in the "release" branch, along with the list of paths 103 each commit modifies. 104 105git log --follow builtin-rev-list.c:: 106 107 Shows the commits that changed builtin-rev-list.c, including 108 those commits that occurred before the file was given its 109 present name. 110 111git log --branches --not --remotes=origin:: 112 113 Shows all commits that are in any of local branches but not in 114 any of remote tracking branches for 'origin' (what you have that 115 origin doesn't). 116 117git log master --not --remotes=*/master:: 118 119 Shows all commits that are in local master but not in any remote 120 repository master branches. 121 122git log -p -m --first-parent:: 123 124 Shows the history including change diffs, but only from the 125 "main branch" perspective, skipping commits that come from merged 126 branches, and showing full diffs of changes introduced by the merges. 127 This makes sense only when following a strict policy of merging all 128 topic branches when staying on a single integration branch. 129 130 131Discussion 132---------- 133 134include::i18n.txt[] 135 136Configuration 137------------- 138 139See linkgit:git-config[1] for core variables and linkgit:git-diff[1] 140for settings related to diff generation. 141 142format.pretty:: 143 Default for the `--format` option. (See "PRETTY FORMATS" above.) 144 Defaults to "medium". 145 146i18n.logOutputEncoding:: 147 Encoding to use when displaying logs. (See "Discussion", above.) 148 Defaults to the value of `i18n.commitEncoding` if set, UTF-8 149 otherwise. 150 151log.date:: 152 Default format for human-readable dates. (Compare the 153 `--date` option.) Defaults to "default", which means to write 154 dates like `Sat May 8 19:35:34 2010 -0500`. 155 156log.showroot:: 157 If `false`, 'git log' and related commands will not treat the 158 initial commit as a big creation event. Any root commits in 159 `git log -p` output would be shown without a diff attached. 160 The default is `true`. 161 162mailmap.file:: 163 See linkgit:git-shortlog[1]. 164 165notes.displayRef:: 166 Which refs, in addition to the default set by `core.notesRef` 167 or 'GIT_NOTES_REF', to read notes from when showing commit 168 messages with the 'log' family of commands. See 169 linkgit:git-notes[1]. 170+ 171May be an unabbreviated ref name or a glob and may be specified 172multiple times. A warning will be issued for refs that do not exist, 173but a glob that does not match any refs is silently ignored. 174+ 175This setting can be disabled by the `--no-standard-notes` option, 176overridden by the 'GIT_NOTES_DISPLAY_REF' environment variable, 177and supplemented by the `--show-notes` option. 178 179Author 180------ 181Written by Linus Torvalds <torvalds@osdl.org> 182 183Documentation 184-------------- 185Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>. 186 187GIT 188--- 189Part of the linkgit:git[1] suite