Google Git
Sign in
chromium / external / gitster / git-htmldocs / f9771f69968326f60eaa1b69efe27a302998c755 / . / git-rev-list.html
blob: ecf560fe5e62c2b268cc37c116114356baf55e66 [file] [log] [blame]
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
4<head>
5<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
Junio C Hamano5f327762006-03-02 09:14:51[diff] [blame]6<meta name="generator" content="AsciiDoc 7.0.2" />
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]7<style type="text/css">
8/* Debug borders */
9p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
10/*
11 border: 1px solid red;
12*/
13}
14
15body {
16 margin: 1em 5% 1em 5%;
17}
18
19a { color: blue; }
20a:visited { color: fuchsia; }
21
22em {
23 font-style: italic;
24}
25
26strong {
27 font-weight: bold;
28}
29
30tt {
31 color: navy;
32}
33
34h1, h2, h3, h4, h5, h6 {
35 color: #527bbd;
36 font-family: sans-serif;
37 margin-top: 1.2em;
38 margin-bottom: 0.5em;
39 line-height: 1.3;
40}
41
42h1 {
43 border-bottom: 2px solid silver;
44}
45h2 {
46 border-bottom: 2px solid silver;
47 padding-top: 0.5em;
48}
49
50div.sectionbody {
51 font-family: serif;
52 margin-left: 0;
53}
54
55hr {
56 border: 1px solid silver;
57}
58
59p {
60 margin-top: 0.5em;
61 margin-bottom: 0.5em;
62}
63
64pre {
65 padding: 0;
66 margin: 0;
67}
68
69span#author {
70 color: #527bbd;
71 font-family: sans-serif;
72 font-weight: bold;
73 font-size: 1.2em;
74}
75span#email {
76}
77span#revision {
78 font-family: sans-serif;
79}
80
81div#footer {
82 font-family: sans-serif;
83 font-size: small;
84 border-top: 2px solid silver;
85 padding-top: 0.5em;
86 margin-top: 4.0em;
87}
88div#footer-text {
89 float: left;
90 padding-bottom: 0.5em;
91}
92div#footer-badges {
93 float: right;
94 padding-bottom: 0.5em;
95}
96
97div#preamble,
98div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
99div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
100div.admonitionblock {
101 margin-right: 10%;
102 margin-top: 1.5em;
103 margin-bottom: 1.5em;
104}
105div.admonitionblock {
106 margin-top: 2.5em;
107 margin-bottom: 2.5em;
108}
109
110div.content { /* Block element content. */
111 padding: 0;
112}
113
114/* Block element titles. */
115div.title, caption.title {
116 font-family: sans-serif;
117 font-weight: bold;
118 text-align: left;
119 margin-top: 1.0em;
120 margin-bottom: 0.5em;
121}
122div.title + * {
123 margin-top: 0;
124}
125
126td div.title:first-child {
127 margin-top: 0.0em;
128}
129div.content div.title:first-child {
130 margin-top: 0.0em;
131}
132div.content + div.title {
133 margin-top: 0.0em;
134}
135
136div.sidebarblock > div.content {
137 background: #ffffee;
138 border: 1px solid silver;
139 padding: 0.5em;
140}
141
142div.listingblock > div.content {
143 border: 1px solid silver;
144 background: #f4f4f4;
145 padding: 0.5em;
146}
147
148div.quoteblock > div.content {
149 padding-left: 2.0em;
150}
151div.quoteblock .attribution {
152 text-align: right;
153}
154
155div.admonitionblock .icon {
156 vertical-align: top;
157 font-size: 1.1em;
158 font-weight: bold;
159 text-decoration: underline;
160 color: #527bbd;
161 padding-right: 0.5em;
162}
163div.admonitionblock td.content {
164 padding-left: 0.5em;
165 border-left: 2px solid silver;
166}
167
168div.exampleblock > div.content {
169 border-left: 2px solid silver;
170 padding: 0.5em;
171}
172
173div.verseblock div.content {
174 white-space: pre;
175}
176
177div.imageblock div.content { padding-left: 0; }
178div.imageblock img { border: 1px solid silver; }
179span.image img { border-style: none; }
180
181dl {
182 margin-top: 0.8em;
183 margin-bottom: 0.8em;
184}
185dt {
186 margin-top: 0.5em;
187 margin-bottom: 0;
188 font-style: italic;
189}
190dd > *:first-child {
191 margin-top: 0;
192}
193
194ul, ol {
195 list-style-position: outside;
196}
197ol.olist2 {
198 list-style-type: lower-alpha;
199}
200
201div.tableblock > table {
202 border-color: #527bbd;
203 border-width: 3px;
204}
205thead {
206 font-family: sans-serif;
207 font-weight: bold;
208}
209tfoot {
210 font-weight: bold;
211}
212
213div.hlist {
214 margin-top: 0.8em;
215 margin-bottom: 0.8em;
216}
217td.hlist1 {
218 vertical-align: top;
219 font-style: italic;
220 padding-right: 0.8em;
221}
222td.hlist2 {
223 vertical-align: top;
224}
225
226@media print {
227 div#footer-badges { display: none; }
228}
229include::./stylesheets/xhtml11-manpage.css[]
230/* Workarounds for IE6's broken and incomplete CSS2. */
231
232div.sidebar-content {
233 background: #ffffee;
234 border: 1px solid silver;
235 padding: 0.5em;
236}
237div.sidebar-title, div.image-title {
238 font-family: sans-serif;
239 font-weight: bold;
240 margin-top: 0.0em;
241 margin-bottom: 0.5em;
242}
243
244div.listingblock div.content {
245 border: 1px solid silver;
246 background: #f4f4f4;
247 padding: 0.5em;
248}
249
250div.quoteblock-content {
251 padding-left: 2.0em;
252}
253
254div.exampleblock-content {
255 border-left: 2px solid silver;
256 padding-left: 0.5em;
257}
258</style>
259<title>git-rev-list(1)</title>
260</head>
261<body>
262<div id="header">
263<h1>
264git-rev-list(1) Manual Page
265</h1>
266<h2>NAME</h2>
267<div class="sectionbody">
268<p>git-rev-list -
269 Lists commit objects in reverse chronological order
270</p>
271</div>
272</div>
273<h2>SYNOPSIS</h2>
274<div class="sectionbody">
Junio C Hamano235a91e2006-01-07 01:13:58[diff] [blame]275<div class="verseblock">
276<div class="content"><em>git-rev-list</em> [ --max-count=number ]
Junio C Hamano17bbaca2006-12-25 11:36:31[diff] [blame]277 [ --skip=number ]
Junio C Hamano235a91e2006-01-07 01:13:58[diff] [blame]278 [ --max-age=timestamp ]
279 [ --min-age=timestamp ]
280 [ --sparse ]
281 [ --no-merges ]
Junio C Hamano9be18972006-01-28 08:54:57[diff] [blame]282 [ --remove-empty ]
Junio C Hamano872c5682006-07-07 06:05:40[diff] [blame]283 [ --not ]
Junio C Hamano235a91e2006-01-07 01:13:58[diff] [blame]284 [ --all ]
Junio C Hamanoc9245d92006-09-06 09:35:46[diff] [blame]285 [ --stdin ]
Junio C Hamanodecf50e2006-03-05 10:51:14[diff] [blame]286 [ --topo-order ]
Junio C Hamano235a91e2006-01-07 01:13:58[diff] [blame]287 [ --parents ]
Junio C Hamano775a0f42006-12-31 01:19:14[diff] [blame]288 [ --encoding[=&lt;encoding&gt;] ]
Junio C Hamano47c1e3c2006-09-25 04:45:55[diff] [blame]289 [ --(author|committer|grep)=&lt;pattern&gt; ]
Junio C Hamano5f327762006-03-02 09:14:51[diff] [blame]290 [ [--objects | --objects-edge] [ --unpacked ] ]
Junio C Hamano235a91e2006-01-07 01:13:58[diff] [blame]291 [ --pretty | --header ]
292 [ --bisect ]
Junio C Hamano859f3b42006-08-04 10:04:30[diff] [blame]293 [ --merge ]
Junio C Hamano235a91e2006-01-07 01:13:58[diff] [blame]294 &lt;commit&gt;&#8230; [ -- &lt;paths&gt;&#8230; ]</div></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]295</div>
296<h2>DESCRIPTION</h2>
297<div class="sectionbody">
298<p>Lists commit objects in reverse chronological order starting at the
299given commit(s), taking ancestry relationship into account. This is
300useful to produce human-readable log output.</p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]301<p>Commits which are stated with a preceding <em>^</em> cause listing to
302stop at that point. Their parents are implied. Thus the following
303command:</p>
304<div class="listingblock">
305<div class="content">
306<pre><tt> $ git-rev-list foo bar ^baz</tt></pre>
307</div></div>
308<p>means "list all the commits which are included in <em>foo</em> and <em>bar</em>, but
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]309not in <em>baz</em>".</p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]310<p>A special notation "<em>&lt;commit1&gt;</em>..<em>&lt;commit2&gt;</em>" can be used as a
311short-hand for "^<em>&lt;commit1&gt;</em> <em>&lt;commit2&gt;</em>". For example, either of
312the following may be used interchangeably:</p>
313<div class="listingblock">
314<div class="content">
315<pre><tt> $ git-rev-list origin..HEAD
316 $ git-rev-list HEAD ^origin</tt></pre>
317</div></div>
318<p>Another special notation is "<em>&lt;commit1&gt;</em>&#8230;<em>&lt;commit2&gt;</em>" which is useful
319for merges. The resulting set of commits is the symmetric difference
Junio C Hamano872c5682006-07-07 06:05:40[diff] [blame]320between the two operands. The following two commands are equivalent:</p>
321<div class="listingblock">
322<div class="content">
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]323<pre><tt> $ git-rev-list A B --not $(git-merge-base --all A B)
324 $ git-rev-list A...B</tt></pre>
Junio C Hamano872c5682006-07-07 06:05:40[diff] [blame]325</div></div>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]326<p><a href="git-rev-list.html">git-rev-list(1)</a> is a very essential git program, since it
327provides the ability to build and traverse commit ancestry graphs. For
328this reason, it has a lot of different options that enables it to be
329used by commands as different as <a href="git-bisect.html">git-bisect(1)</a> and
330<a href="git-repack.html">git-repack(1)</a>.</p>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]331</div>
332<h2>OPTIONS</h2>
333<div class="sectionbody">
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]334<h3>Commit Formatting</h3>
335<p>Using these options, <a href="git-rev-list.html">git-rev-list(1)</a> will act similar to the
336more specialized family of commit log tools: <a href="git-log.html">git-log(1)</a>,
337<a href="git-show.html">git-show(1)</a>, and <a href="git-whatchanged.html">git-whatchanged(1)</a></p>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]338<dl>
339<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]340--pretty[=<em>&lt;format&gt;</em>]
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]341</dt>
342<dd>
343<p>
Junio C Hamanoa340aaa2006-11-23 02:47:33[diff] [blame]344 Pretty-prints the details of a commit. <tt>--pretty</tt>
345 without an explicit <tt>=&lt;format&gt;</tt> defaults to <em>medium</em>.
346 If the commit is a merge, and if the pretty-format
347 is not <em>oneline</em>, <em>email</em> or <em>raw</em>, an additional line is
348 inserted before the <em>Author:</em> line. This line begins with
349 "Merge: " and the sha1s of ancestral commits are printed,
350 separated by spaces. Note that the listed commits may not
351 necessarily be the list of the <strong>direct</strong> parent commits if you
352 have limited your view of history: for example, if you are
353 only interested in changes related to a certain directory or
354 file. Here are some additional details for each format:
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]355</p>
Junio C Hamanoa340aaa2006-11-23 02:47:33[diff] [blame]356<ul>
357<li>
358<p>
359<em>oneline</em>
360</p>
361<div class="literalblock">
362<div class="content">
363<pre><tt>&lt;sha1&gt; &lt;title line&gt;</tt></pre>
364</div></div>
365<p>This is designed to be as compact as possible.</p>
366</li>
367<li>
368<p>
369<em>short</em>
370</p>
371<div class="literalblock">
372<div class="content">
373<pre><tt>commit &lt;sha1&gt;
374Author: &lt;author&gt;</tt></pre>
375</div></div>
376<div class="literalblock">
377<div class="content">
378<pre><tt>&lt;title line&gt;</tt></pre>
379</div></div>
380</li>
381<li>
382<p>
383<em>medium</em>
384</p>
385<div class="literalblock">
386<div class="content">
387<pre><tt>commit &lt;sha1&gt;
388Author: &lt;author&gt;
389Date: &lt;date&gt;</tt></pre>
390</div></div>
391<div class="literalblock">
392<div class="content">
393<pre><tt>&lt;title line&gt;</tt></pre>
394</div></div>
395<div class="literalblock">
396<div class="content">
397<pre><tt>&lt;full commit message&gt;</tt></pre>
398</div></div>
399</li>
400<li>
401<p>
402<em>full</em>
403</p>
404<div class="literalblock">
405<div class="content">
406<pre><tt>commit &lt;sha1&gt;
407Author: &lt;author&gt;
408Commit: &lt;committer&gt;</tt></pre>
409</div></div>
410<div class="literalblock">
411<div class="content">
412<pre><tt>&lt;title line&gt;</tt></pre>
413</div></div>
414<div class="literalblock">
415<div class="content">
416<pre><tt>&lt;full commit message&gt;</tt></pre>
417</div></div>
418</li>
419<li>
420<p>
421<em>fuller</em>
422</p>
423<div class="literalblock">
424<div class="content">
425<pre><tt>commit &lt;sha1&gt;
426Author: &lt;author&gt;
427AuthorDate: &lt;date &amp; time&gt;
428Commit: &lt;committer&gt;
429CommitDate: &lt;date &amp; time&gt;</tt></pre>
430</div></div>
431<div class="literalblock">
432<div class="content">
433<pre><tt>&lt;title line&gt;</tt></pre>
434</div></div>
435<div class="literalblock">
436<div class="content">
437<pre><tt>&lt;full commit message&gt;</tt></pre>
438</div></div>
439</li>
440<li>
441<p>
442<em>email</em>
443</p>
444<div class="literalblock">
445<div class="content">
446<pre><tt>From &lt;sha1&gt; &lt;date&gt;
447From: &lt;author&gt;
448Date: &lt;date &amp; time&gt;
449Subject: [PATCH] &lt;title line&gt;</tt></pre>
450</div></div>
451<div class="literalblock">
452<div class="content">
453<pre><tt>full commit message&gt;</tt></pre>
454</div></div>
455</li>
456<li>
457<p>
458<em>raw</em>
459</p>
460<p>The <em>raw</em> format shows the entire commit exactly as
461stored in the commit object. Notably, the SHA1s are
462displayed in full, regardless of whether --abbrev or
463--no-abbrev are used, and <em>parents</em> information show the
464true parent commits, without taking grafts nor history
465simplification into account.</p>
466</li>
467</ul>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]468</dd>
469<dt>
Junio C Hamano775a0f42006-12-31 01:19:14[diff] [blame]470--encoding[=&lt;encoding&gt;]
471</dt>
472<dd>
473<p>
474 The commit objects record the encoding used for the log message
475 in their encoding header; this option can be used to tell the
476 command to re-code the commit log message in the encoding
477 preferred by the user. For non plumbing commands this
478 defaults to UTF-8.
479</p>
480</dd>
481<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]482--relative-date
483</dt>
484<dd>
485<p>
486 Show dates relative to the current time, e.g. "2 hours ago".
487 Only takes effect for dates shown in human-readable format, such
488 as when using "--pretty".
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]489</p>
490</dd>
491<dt>
492--header
493</dt>
494<dd>
495<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]496 Print the contents of the commit in raw-format; each record is
497 separated with a NUL character.
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]498</p>
499</dd>
500<dt>
Junio C Hamano7ccb9fd2006-07-15 01:38:40[diff] [blame]501--parents
502</dt>
503<dd>
504<p>
505 Print the parents of the commit.
506</p>
507</dd>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]508</dl>
509<h3>Diff Formatting</h3>
510<p>Below are listed options that control the formatting of diff output.
511Some of them are specific to <a href="git-rev-list.html">git-rev-list(1)</a>, however other diff
512options may be given. See <a href="git-diff-files.html">git-diff-files(1)</a> for more options.</p>
513<dl>
Junio C Hamano7ccb9fd2006-07-15 01:38:40[diff] [blame]514<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]515-c
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]516</dt>
517<dd>
518<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]519 This flag changes the way a merge commit is displayed. It shows
520 the differences from each of the parents to the merge result
521 simultaneously instead of showing pairwise diff between a parent
522 and the result one at a time. Furthermore, it lists only files
523 which were modified from all parents.
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]524</p>
525</dd>
526<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]527--cc
Junio C Hamano5f327762006-03-02 09:14:51[diff] [blame]528</dt>
529<dd>
530<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]531 This flag implies the <em>-c</em> options and further compresses the
532 patch output by omitting hunks that show differences from only
533 one parent, or show the same change from all but one parent for
534 an Octopus merge.
Junio C Hamano5f327762006-03-02 09:14:51[diff] [blame]535</p>
536</dd>
537<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]538-r
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]539</dt>
540<dd>
541<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]542 Show recursive diffs.
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]543</p>
544</dd>
545<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]546-t
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]547</dt>
548<dd>
549<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]550 Show the tree objects in the diff output. This implies <em>-r</em>.
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]551</p>
552</dd>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]553</dl>
554<h3>Commit Limiting</h3>
555<p>Besides specifying a range of commits that should be listed using the
556special notations explained in the description, additional commit
557limiting may be applied.</p>
558<dl>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]559<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]560-n <em>number</em>, --max-count=<em>number</em>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]561</dt>
562<dd>
563<p>
564 Limit the number of commits output.
565</p>
566</dd>
567<dt>
Junio C Hamano17bbaca2006-12-25 11:36:31[diff] [blame]568--skip=<em>number</em>
569</dt>
570<dd>
571<p>
572 Skip <em>number</em> commits before starting to show the commit output.
573</p>
574</dd>
575<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]576--since=<em>date</em>, --after=<em>date</em>
577</dt>
578<dd>
579<p>
580 Show commits more recent than a specific date.
581</p>
582</dd>
583<dt>
584--until=<em>date</em>, --before=<em>date</em>
585</dt>
586<dd>
587<p>
588 Show commits older than a specific date.
589</p>
590</dd>
591<dt>
592--max-age=<em>timestamp</em>, --min-age=<em>timestamp</em>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]593</dt>
594<dd>
595<p>
596 Limit the commits output to specified time range.
597</p>
598</dd>
599<dt>
Junio C Hamano47c1e3c2006-09-25 04:45:55[diff] [blame]600--author=<em>pattern</em>, --committer=<em>pattern</em>
601</dt>
602<dd>
603<p>
604 Limit the commits output to ones with author/committer
605 header lines that match the specified pattern.
606</p>
607</dd>
608<dt>
609--grep=<em>pattern</em>
610</dt>
611<dd>
612<p>
613 Limit the commits output to ones with log message that
614 matches the specified pattern.
615</p>
616</dd>
617<dt>
Junio C Hamano9be18972006-01-28 08:54:57[diff] [blame]618--remove-empty
619</dt>
620<dd>
621<p>
622 Stop when a given path disappears from the tree.
623</p>
624</dd>
625<dt>
Junio C Hamano7ccb9fd2006-07-15 01:38:40[diff] [blame]626--no-merges
627</dt>
628<dd>
629<p>
630 Do not print commits with more than one parent.
631</p>
632</dd>
633<dt>
Junio C Hamano872c5682006-07-07 06:05:40[diff] [blame]634--not
635</dt>
636<dd>
637<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]638 Reverses the meaning of the <em>^</em> prefix (or lack thereof)
639 for all following revision specifiers, up to the next <em>--not</em>.
Junio C Hamano872c5682006-07-07 06:05:40[diff] [blame]640</p>
641</dd>
642<dt>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]643--all
644</dt>
645<dd>
646<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]647 Pretend as if all the refs in <tt>$GIT_DIR/refs/</tt> are listed on the
648 command line as <em>&lt;commit&gt;</em>.
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]649</p>
650</dd>
Junio C Hamano859f3b42006-08-04 10:04:30[diff] [blame]651<dt>
Junio C Hamanoc9245d92006-09-06 09:35:46[diff] [blame]652--stdin
653</dt>
654<dd>
655<p>
656 In addition to the <em>&lt;commit&gt;</em> listed on the command
657 line, read them from the standard input.
658</p>
659</dd>
660<dt>
Junio C Hamano859f3b42006-08-04 10:04:30[diff] [blame]661--merge
662</dt>
663<dd>
664<p>
665 After a failed merge, show refs that touch files having a
666 conflict and don't exist on all heads to merge.
667</p>
668</dd>
Junio C Hamanoa0778c92006-08-29 04:03:11[diff] [blame]669<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]670--boundary
Junio C Hamanoa0778c92006-08-29 04:03:11[diff] [blame]671</dt>
672<dd>
673<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]674 Output uninteresting commits at the boundary, which are usually
675 not shown.
676</p>
677</dd>
678<dt>
679--dense, --sparse
680</dt>
681<dd>
682<p>
683When optional paths are given, the default behaviour (<em>--dense</em>) is to
684only output commits that changes at least one of them, and also ignore
685merges that do not touch the given paths.
686</p>
687<p>Use the <em>--sparse</em> flag to makes the command output all eligible commits
688(still subject to count and age limitation), but apply merge
689simplification nevertheless.</p>
690</dd>
691<dt>
692--bisect
693</dt>
694<dd>
695<p>
696Limit output to the one commit object which is roughly halfway between
697the included and excluded commits. Thus, if
698</p>
699<div class="listingblock">
700<div class="content">
701<pre><tt> $ git-rev-list --bisect foo ^bar ^baz</tt></pre>
702</div></div>
703<p>outputs <em>midpoint</em>, the output of the two commands</p>
704<div class="listingblock">
705<div class="content">
706<pre><tt> $ git-rev-list foo ^midpoint
707 $ git-rev-list midpoint ^bar ^baz</tt></pre>
708</div></div>
709<p>would be of roughly the same length. Finding the change which
710introduces a regression is thus reduced to a binary search: repeatedly
711generate and test new 'midpoint's until the commit chain is of length
712one.</p>
713</dd>
714</dl>
715<h3>Commit Ordering</h3>
716<p>By default, the commits are shown in reverse chronological order.</p>
717<dl>
718<dt>
719--topo-order
720</dt>
721<dd>
722<p>
723 This option makes them appear in topological order (i.e.
724 descendant commits are shown before their parents).
725</p>
726</dd>
727<dt>
728--date-order
729</dt>
730<dd>
731<p>
732 This option is similar to <em>--topo-order</em> in the sense that no
733 parent comes before all of its children, but otherwise things
734 are still ordered in the commit timestamp order.
735</p>
736</dd>
737</dl>
738<h3>Object Traversal</h3>
739<p>These options are mostly targeted for packing of git repositories.</p>
740<dl>
741<dt>
742--objects
743</dt>
744<dd>
745<p>
746 Print the object IDs of any object referenced by the listed
747 commits. <em>git-rev-list --objects foo ^bar</em> thus means "send me
748 all object IDs which I need to download if I have the commit
749 object <em>bar</em>, but not <em>foo</em>".
750</p>
751</dd>
752<dt>
753--objects-edge
754</dt>
755<dd>
756<p>
757 Similar to <em>--objects</em>, but also print the IDs of excluded
758 commits prefixed with a "-" character. This is used by
759 <a href="git-pack-objects.html">git-pack-objects(1)</a> to build "thin" pack, which records
760 objects in deltified form based on objects contained in these
761 excluded commits to reduce network traffic.
762</p>
763</dd>
764<dt>
765--unpacked
766</dt>
767<dd>
768<p>
769 Only useful with <em>--objects</em>; print the object IDs that are not
770 in packs.
Junio C Hamanoa0778c92006-08-29 04:03:11[diff] [blame]771</p>
772</dd>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]773</dl>
774</div>
775<h2>Author</h2>
776<div class="sectionbody">
777<p>Written by Linus Torvalds &lt;torvalds@osdl.org&gt;</p>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]778</div>
779<h2>Documentation</h2>
780<div class="sectionbody">
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]781<p>Documentation by David Greaves, Junio C Hamano, Jonas Fonseca
782and the git-list &lt;git@vger.kernel.org&gt;.</p>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]783</div>
784<h2>GIT</h2>
785<div class="sectionbody">
786<p>Part of the <a href="git.html">git(7)</a> suite</p>
787</div>
788<div id="footer">
789<div id="footer-text">
Junio C Hamano775a0f42006-12-31 01:19:14[diff] [blame]790Last updated 31-Dec-2006 01:19:04 UTC
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]791</div>
792</div>
793</body>
794</html>