1Commit Formatting 2~~~~~~~~~~~~~~~~~ 3 4ifdef::git-rev-list[] 5Using these options, linkgit:git-rev-list[1] will act similar to the 6more specialized family of commit log tools: linkgit:git-log[1], 7linkgit:git-show[1], and linkgit:git-whatchanged[1] 8endif::git-rev-list[] 9 10include::pretty-options.txt[] 11 12--relative-date:: 13 14 Synonym for `--date=relative`. 15 16--date={relative,local,default,iso,rfc}:: 17 18 Only takes effect for dates shown in human-readable format, such 19 as when using "--pretty". 20+ 21`--date=relative` shows dates relative to the current time, 22e.g. "2 hours ago". 23+ 24`--date=local` shows timestamps in user's local timezone. 25+ 26`--date=iso` (or `--date=iso8601`) shows timestamps in ISO 8601 format. 27+ 28`--date=rfc` (or `--date=rfc2822`) shows timestamps in RFC 2822 29format, often found in E-mail messages. 30+ 31`--date=short` shows only date but not time, in `YYYY-MM-DD` format. 32+ 33`--date=default` shows timestamps in the original timezone 34(either committer's or author's). 35 36--header:: 37 38 Print the contents of the commit in raw-format; each record is 39 separated with a NUL character. 40 41--parents:: 42 43 Print the parents of the commit. 44 45--timestamp:: 46 Print the raw commit timestamp. 47 48--left-right:: 49 50 Mark which side of a symmetric diff a commit is reachable from. 51 Commits from the left side are prefixed with `<` and those from 52 the right with `>`. If combined with `--boundary`, those 53 commits are prefixed with `-`. 54+ 55For example, if you have this topology: 56+ 57----------------------------------------------------------------------- 58 y---b---b branch B 59 / \ / 60 / . 61 / / \ 62 o---x---a---a branch A 63----------------------------------------------------------------------- 64+ 65you would get an output line this: 66+ 67----------------------------------------------------------------------- 68 $ git rev-list --left-right --boundary --pretty=oneline A...B 69 70 >bbbbbbb... 3rd on b 71 >bbbbbbb... 2nd on b 72 <aaaaaaa... 3rd on a 73 <aaaaaaa... 2nd on a 74 -yyyyyyy... 1st on b 75 -xxxxxxx... 1st on a 76----------------------------------------------------------------------- 77 78--graph:: 79 80 Draw a text-based graphical representation of the commit history 81 on the left hand side of the output. This may cause extra lines 82 to be printed in between commits, in order for the graph history 83 to be drawn properly. 84+ 85This implies the '--topo-order' option by default, but the 86'--date-order' option may also be specified. 87 88Diff Formatting 89~~~~~~~~~~~~~~~ 90 91Below are listed options that control the formatting of diff output. 92Some of them are specific to linkgit:git-rev-list[1], however other diff 93options may be given. See linkgit:git-diff-files[1] for more options. 94 95-c:: 96 97 This flag changes the way a merge commit is displayed. It shows 98 the differences from each of the parents to the merge result 99 simultaneously instead of showing pairwise diff between a parent 100 and the result one at a time. Furthermore, it lists only files 101 which were modified from all parents. 102 103--cc:: 104 105 This flag implies the '-c' options and further compresses the 106 patch output by omitting hunks that show differences from only 107 one parent, or show the same change from all but one parent for 108 an Octopus merge. 109 110-r:: 111 112 Show recursive diffs. 113 114-t:: 115 116 Show the tree objects in the diff output. This implies '-r'. 117 118Commit Limiting 119~~~~~~~~~~~~~~~ 120 121Besides specifying a range of commits that should be listed using the 122special notations explained in the description, additional commit 123limiting may be applied. 124 125-- 126 127-n 'number', --max-count='number':: 128 129 Limit the number of commits output. 130 131--skip='number':: 132 133 Skip 'number' commits before starting to show the commit output. 134 135--since='date', --after='date':: 136 137 Show commits more recent than a specific date. 138 139--until='date', --before='date':: 140 141 Show commits older than a specific date. 142 143ifdef::git-rev-list[] 144--max-age='timestamp', --min-age='timestamp':: 145 146 Limit the commits output to specified time range. 147endif::git-rev-list[] 148 149--author='pattern', --committer='pattern':: 150 151 Limit the commits output to ones with author/committer 152 header lines that match the specified pattern (regular expression). 153 154--grep='pattern':: 155 156 Limit the commits output to ones with log message that 157 matches the specified pattern (regular expression). 158 159-i, --regexp-ignore-case:: 160 161 Match the regexp limiting patterns without regard to letters case. 162 163-E, --extended-regexp:: 164 165 Consider the limiting patterns to be extended regular expressions 166 instead of the default basic regular expressions. 167 168-F, --fixed-strings:: 169 170 Consider the limiting patterns to be fixed strings (don't interpret 171 pattern as a regular expression). 172 173--remove-empty:: 174 175 Stop when a given path disappears from the tree. 176 177--full-history:: 178 179 Show also parts of history irrelevant to current state of a given 180 path. This turns off history simplification, which removed merges 181 which didn't change anything at all at some child. It will still actually 182 simplify away merges that didn't change anything at all into either 183 child. 184 185--no-merges:: 186 187 Do not print commits with more than one parent. 188 189--first-parent:: 190 Follow only the first parent commit upon seeing a merge 191 commit. This option can give a better overview when 192 viewing the evolution of a particular topic branch, 193 because merges into a topic branch tend to be only about 194 adjusting to updated upstream from time to time, and 195 this option allows you to ignore the individual commits 196 brought in to your history by such a merge. 197 198--not:: 199 200 Reverses the meaning of the '{caret}' prefix (or lack thereof) 201 for all following revision specifiers, up to the next '--not'. 202 203--all:: 204 205 Pretend as if all the refs in `$GIT_DIR/refs/` are listed on the 206 command line as '<commit>'. 207 208--stdin:: 209 210 In addition to the '<commit>' listed on the command 211 line, read them from the standard input. 212 213--quiet:: 214 215 Don't print anything to standard output. This form 216 is primarily meant to allow the caller to 217 test the exit status to see if a range of objects is fully 218 connected (or not). It is faster than redirecting stdout 219 to /dev/null as the output does not have to be formatted. 220 221--cherry-pick:: 222 223 Omit any commit that introduces the same change as 224 another commit on the "other side" when the set of 225 commits are limited with symmetric difference. 226+ 227For example, if you have two branches, `A` and `B`, a usual way 228to list all commits on only one side of them is with 229`--left-right`, like the example above in the description of 230that option. It however shows the commits that were cherry-picked 231from the other branch (for example, "3rd on b" may be cherry-picked 232from branch A). With this option, such pairs of commits are 233excluded from the output. 234 235-g, --walk-reflogs:: 236 237 Instead of walking the commit ancestry chain, walk 238 reflog entries from the most recent one to older ones. 239 When this option is used you cannot specify commits to 240 exclude (that is, '{caret}commit', 'commit1..commit2', 241 nor 'commit1...commit2' notations cannot be used). 242+ 243With '\--pretty' format other than oneline (for obvious reasons), 244this causes the output to have two extra lines of information 245taken from the reflog. By default, 'commit@\{Nth}' notation is 246used in the output. When the starting commit is specified as 247'commit@{now}', output also uses 'commit@\{timestamp}' notation 248instead. Under '\--pretty=oneline', the commit message is 249prefixed with this information on the same line. 250 251Cannot be combined with '\--reverse'. 252See also linkgit:git-reflog[1]. 253 254--merge:: 255 256 After a failed merge, show refs that touch files having a 257 conflict and don't exist on all heads to merge. 258 259--boundary:: 260 261 Output uninteresting commits at the boundary, which are usually 262 not shown. 263 264--dense, --sparse:: 265 266When optional paths are given, the default behaviour ('--dense') is to 267only output commits that changes at least one of them, and also ignore 268merges that do not touch the given paths. 269 270Use the '--sparse' flag to makes the command output all eligible commits 271(still subject to count and age limitation), but apply merge 272simplification nevertheless. 273 274ifdef::git-rev-list[] 275--bisect:: 276 277Limit output to the one commit object which is roughly halfway between 278the included and excluded commits. Thus, if 279 280----------------------------------------------------------------------- 281 $ git-rev-list --bisect foo ^bar ^baz 282----------------------------------------------------------------------- 283 284outputs 'midpoint', the output of the two commands 285 286----------------------------------------------------------------------- 287 $ git-rev-list foo ^midpoint 288 $ git-rev-list midpoint ^bar ^baz 289----------------------------------------------------------------------- 290 291would be of roughly the same length. Finding the change which 292introduces a regression is thus reduced to a binary search: repeatedly 293generate and test new 'midpoint's until the commit chain is of length 294one. 295 296--bisect-vars:: 297 298This calculates the same as `--bisect`, but outputs text ready 299to be eval'ed by the shell. These lines will assign the name of 300the midpoint revision to the variable `bisect_rev`, and the 301expected number of commits to be tested after `bisect_rev` is 302tested to `bisect_nr`, the expected number of commits to be 303tested if `bisect_rev` turns out to be good to `bisect_good`, 304the expected number of commits to be tested if `bisect_rev` 305turns out to be bad to `bisect_bad`, and the number of commits 306we are bisecting right now to `bisect_all`. 307 308--bisect-all:: 309 310This outputs all the commit objects between the included and excluded 311commits, ordered by their distance to the included and excluded 312commits. The farthest from them is displayed first. (This is the only 313one displayed by `--bisect`.) 314 315This is useful because it makes it easy to choose a good commit to 316test when you want to avoid to test some of them for some reason (they 317may not compile for example). 318 319This option can be used along with `--bisect-vars`, in this case, 320after all the sorted commit objects, there will be the same text as if 321`--bisect-vars` had been used alone. 322endif::git-rev-list[] 323 324-- 325 326Commit Ordering 327~~~~~~~~~~~~~~~ 328 329By default, the commits are shown in reverse chronological order. 330 331--topo-order:: 332 333 This option makes them appear in topological order (i.e. 334 descendant commits are shown before their parents). 335 336--date-order:: 337 338 This option is similar to '--topo-order' in the sense that no 339 parent comes before all of its children, but otherwise things 340 are still ordered in the commit timestamp order. 341 342--reverse:: 343 344 Output the commits in reverse order. 345 Cannot be combined with '\--walk-reflogs'. 346 347Object Traversal 348~~~~~~~~~~~~~~~~ 349 350These options are mostly targeted for packing of git repositories. 351 352--objects:: 353 354 Print the object IDs of any object referenced by the listed 355 commits. '--objects foo ^bar' thus means "send me 356 all object IDs which I need to download if I have the commit 357 object 'bar', but not 'foo'". 358 359--objects-edge:: 360 361 Similar to '--objects', but also print the IDs of excluded 362 commits prefixed with a "-" character. This is used by 363 linkgit:git-pack-objects[1] to build "thin" pack, which records 364 objects in deltified form based on objects contained in these 365 excluded commits to reduce network traffic. 366 367--unpacked:: 368 369 Only useful with '--objects'; print the object IDs that are not 370 in packs. 371 372--no-walk:: 373 374 Only show the given revs, but do not traverse their ancestors. 375 376--do-walk:: 377 378 Overrides a previous --no-walk.