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