Google Git
Sign in
chromium / external / gitster / git-htmldocs / 96010b2a3ad29e2413ce39345ebfa2b0b7e09c88 / . / git-rev-list.html
blob: b10c371f21d5afaacfa70bfec02e226f8e8874a6 [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 ]
277 [ --max-age=timestamp ]
278 [ --min-age=timestamp ]
279 [ --sparse ]
280 [ --no-merges ]
Junio C Hamano9be18972006-01-28 08:54:57[diff] [blame]281 [ --remove-empty ]
Junio C Hamano872c5682006-07-07 06:05:40[diff] [blame]282 [ --not ]
Junio C Hamano235a91e2006-01-07 01:13:58[diff] [blame]283 [ --all ]
Junio C Hamanoc9245d92006-09-06 09:35:46[diff] [blame]284 [ --stdin ]
Junio C Hamanodecf50e2006-03-05 10:51:14[diff] [blame]285 [ --topo-order ]
Junio C Hamano235a91e2006-01-07 01:13:58[diff] [blame]286 [ --parents ]
Junio C Hamano47c1e3c2006-09-25 04:45:55[diff] [blame]287 [ --(author|committer|grep)=&lt;pattern&gt; ]
Junio C Hamano5f327762006-03-02 09:14:51[diff] [blame]288 [ [--objects | --objects-edge] [ --unpacked ] ]
Junio C Hamano235a91e2006-01-07 01:13:58[diff] [blame]289 [ --pretty | --header ]
290 [ --bisect ]
Junio C Hamano859f3b42006-08-04 10:04:30[diff] [blame]291 [ --merge ]
Junio C Hamano235a91e2006-01-07 01:13:58[diff] [blame]292 &lt;commit&gt;&#8230; [ -- &lt;paths&gt;&#8230; ]</div></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]293</div>
294<h2>DESCRIPTION</h2>
295<div class="sectionbody">
296<p>Lists commit objects in reverse chronological order starting at the
297given commit(s), taking ancestry relationship into account. This is
298useful to produce human-readable log output.</p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]299<p>Commits which are stated with a preceding <em>^</em> cause listing to
300stop at that point. Their parents are implied. Thus the following
301command:</p>
302<div class="listingblock">
303<div class="content">
304<pre><tt> $ git-rev-list foo bar ^baz</tt></pre>
305</div></div>
306<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]307not in <em>baz</em>".</p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]308<p>A special notation "<em>&lt;commit1&gt;</em>..<em>&lt;commit2&gt;</em>" can be used as a
309short-hand for "^<em>&lt;commit1&gt;</em> <em>&lt;commit2&gt;</em>". For example, either of
310the following may be used interchangeably:</p>
311<div class="listingblock">
312<div class="content">
313<pre><tt> $ git-rev-list origin..HEAD
314 $ git-rev-list HEAD ^origin</tt></pre>
315</div></div>
316<p>Another special notation is "<em>&lt;commit1&gt;</em>&#8230;<em>&lt;commit2&gt;</em>" which is useful
317for merges. The resulting set of commits is the symmetric difference
Junio C Hamano872c5682006-07-07 06:05:40[diff] [blame]318between the two operands. The following two commands are equivalent:</p>
319<div class="listingblock">
320<div class="content">
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]321<pre><tt> $ git-rev-list A B --not $(git-merge-base --all A B)
322 $ git-rev-list A...B</tt></pre>
Junio C Hamano872c5682006-07-07 06:05:40[diff] [blame]323</div></div>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]324<p><a href="git-rev-list.html">git-rev-list(1)</a> is a very essential git program, since it
325provides the ability to build and traverse commit ancestry graphs. For
326this reason, it has a lot of different options that enables it to be
327used by commands as different as <a href="git-bisect.html">git-bisect(1)</a> and
328<a href="git-repack.html">git-repack(1)</a>.</p>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]329</div>
330<h2>OPTIONS</h2>
331<div class="sectionbody">
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]332<h3>Commit Formatting</h3>
333<p>Using these options, <a href="git-rev-list.html">git-rev-list(1)</a> will act similar to the
334more specialized family of commit log tools: <a href="git-log.html">git-log(1)</a>,
335<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]336<dl>
337<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]338--pretty[=<em>&lt;format&gt;</em>]
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]339</dt>
340<dd>
341<p>
Junio C Hamanoa340aaa2006-11-23 02:47:33[diff] [blame]342 Pretty-prints the details of a commit. <tt>--pretty</tt>
343 without an explicit <tt>=&lt;format&gt;</tt> defaults to <em>medium</em>.
344 If the commit is a merge, and if the pretty-format
345 is not <em>oneline</em>, <em>email</em> or <em>raw</em>, an additional line is
346 inserted before the <em>Author:</em> line. This line begins with
347 "Merge: " and the sha1s of ancestral commits are printed,
348 separated by spaces. Note that the listed commits may not
349 necessarily be the list of the <strong>direct</strong> parent commits if you
350 have limited your view of history: for example, if you are
351 only interested in changes related to a certain directory or
352 file. Here are some additional details for each format:
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]353</p>
Junio C Hamanoa340aaa2006-11-23 02:47:33[diff] [blame]354<ul>
355<li>
356<p>
357<em>oneline</em>
358</p>
359<div class="literalblock">
360<div class="content">
361<pre><tt>&lt;sha1&gt; &lt;title line&gt;</tt></pre>
362</div></div>
363<p>This is designed to be as compact as possible.</p>
364</li>
365<li>
366<p>
367<em>short</em>
368</p>
369<div class="literalblock">
370<div class="content">
371<pre><tt>commit &lt;sha1&gt;
372Author: &lt;author&gt;</tt></pre>
373</div></div>
374<div class="literalblock">
375<div class="content">
376<pre><tt>&lt;title line&gt;</tt></pre>
377</div></div>
378</li>
379<li>
380<p>
381<em>medium</em>
382</p>
383<div class="literalblock">
384<div class="content">
385<pre><tt>commit &lt;sha1&gt;
386Author: &lt;author&gt;
387Date: &lt;date&gt;</tt></pre>
388</div></div>
389<div class="literalblock">
390<div class="content">
391<pre><tt>&lt;title line&gt;</tt></pre>
392</div></div>
393<div class="literalblock">
394<div class="content">
395<pre><tt>&lt;full commit message&gt;</tt></pre>
396</div></div>
397</li>
398<li>
399<p>
400<em>full</em>
401</p>
402<div class="literalblock">
403<div class="content">
404<pre><tt>commit &lt;sha1&gt;
405Author: &lt;author&gt;
406Commit: &lt;committer&gt;</tt></pre>
407</div></div>
408<div class="literalblock">
409<div class="content">
410<pre><tt>&lt;title line&gt;</tt></pre>
411</div></div>
412<div class="literalblock">
413<div class="content">
414<pre><tt>&lt;full commit message&gt;</tt></pre>
415</div></div>
416</li>
417<li>
418<p>
419<em>fuller</em>
420</p>
421<div class="literalblock">
422<div class="content">
423<pre><tt>commit &lt;sha1&gt;
424Author: &lt;author&gt;
425AuthorDate: &lt;date &amp; time&gt;
426Commit: &lt;committer&gt;
427CommitDate: &lt;date &amp; time&gt;</tt></pre>
428</div></div>
429<div class="literalblock">
430<div class="content">
431<pre><tt>&lt;title line&gt;</tt></pre>
432</div></div>
433<div class="literalblock">
434<div class="content">
435<pre><tt>&lt;full commit message&gt;</tt></pre>
436</div></div>
437</li>
438<li>
439<p>
440<em>email</em>
441</p>
442<div class="literalblock">
443<div class="content">
444<pre><tt>From &lt;sha1&gt; &lt;date&gt;
445From: &lt;author&gt;
446Date: &lt;date &amp; time&gt;
447Subject: [PATCH] &lt;title line&gt;</tt></pre>
448</div></div>
449<div class="literalblock">
450<div class="content">
451<pre><tt>full commit message&gt;</tt></pre>
452</div></div>
453</li>
454<li>
455<p>
456<em>raw</em>
457</p>
458<p>The <em>raw</em> format shows the entire commit exactly as
459stored in the commit object. Notably, the SHA1s are
460displayed in full, regardless of whether --abbrev or
461--no-abbrev are used, and <em>parents</em> information show the
462true parent commits, without taking grafts nor history
463simplification into account.</p>
464</li>
465</ul>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]466</dd>
467<dt>
468--relative-date
469</dt>
470<dd>
471<p>
472 Show dates relative to the current time, e.g. "2 hours ago".
473 Only takes effect for dates shown in human-readable format, such
474 as when using "--pretty".
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]475</p>
476</dd>
477<dt>
478--header
479</dt>
480<dd>
481<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]482 Print the contents of the commit in raw-format; each record is
483 separated with a NUL character.
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]484</p>
485</dd>
486<dt>
Junio C Hamano7ccb9fd2006-07-15 01:38:40[diff] [blame]487--parents
488</dt>
489<dd>
490<p>
491 Print the parents of the commit.
492</p>
493</dd>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]494</dl>
495<h3>Diff Formatting</h3>
496<p>Below are listed options that control the formatting of diff output.
497Some of them are specific to <a href="git-rev-list.html">git-rev-list(1)</a>, however other diff
498options may be given. See <a href="git-diff-files.html">git-diff-files(1)</a> for more options.</p>
499<dl>
Junio C Hamano7ccb9fd2006-07-15 01:38:40[diff] [blame]500<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]501-c
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]502</dt>
503<dd>
504<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]505 This flag changes the way a merge commit is displayed. It shows
506 the differences from each of the parents to the merge result
507 simultaneously instead of showing pairwise diff between a parent
508 and the result one at a time. Furthermore, it lists only files
509 which were modified from all parents.
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]510</p>
511</dd>
512<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]513--cc
Junio C Hamano5f327762006-03-02 09:14:51[diff] [blame]514</dt>
515<dd>
516<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]517 This flag implies the <em>-c</em> options and further compresses the
518 patch output by omitting hunks that show differences from only
519 one parent, or show the same change from all but one parent for
520 an Octopus merge.
Junio C Hamano5f327762006-03-02 09:14:51[diff] [blame]521</p>
522</dd>
523<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]524-r
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]525</dt>
526<dd>
527<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]528 Show recursive diffs.
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]529</p>
530</dd>
531<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]532-t
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]533</dt>
534<dd>
535<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]536 Show the tree objects in the diff output. This implies <em>-r</em>.
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]537</p>
538</dd>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]539</dl>
540<h3>Commit Limiting</h3>
541<p>Besides specifying a range of commits that should be listed using the
542special notations explained in the description, additional commit
543limiting may be applied.</p>
544<dl>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]545<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]546-n <em>number</em>, --max-count=<em>number</em>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]547</dt>
548<dd>
549<p>
550 Limit the number of commits output.
551</p>
552</dd>
553<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]554--since=<em>date</em>, --after=<em>date</em>
555</dt>
556<dd>
557<p>
558 Show commits more recent than a specific date.
559</p>
560</dd>
561<dt>
562--until=<em>date</em>, --before=<em>date</em>
563</dt>
564<dd>
565<p>
566 Show commits older than a specific date.
567</p>
568</dd>
569<dt>
570--max-age=<em>timestamp</em>, --min-age=<em>timestamp</em>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]571</dt>
572<dd>
573<p>
574 Limit the commits output to specified time range.
575</p>
576</dd>
577<dt>
Junio C Hamano47c1e3c2006-09-25 04:45:55[diff] [blame]578--author=<em>pattern</em>, --committer=<em>pattern</em>
579</dt>
580<dd>
581<p>
582 Limit the commits output to ones with author/committer
583 header lines that match the specified pattern.
584</p>
585</dd>
586<dt>
587--grep=<em>pattern</em>
588</dt>
589<dd>
590<p>
591 Limit the commits output to ones with log message that
592 matches the specified pattern.
593</p>
594</dd>
595<dt>
Junio C Hamano9be18972006-01-28 08:54:57[diff] [blame]596--remove-empty
597</dt>
598<dd>
599<p>
600 Stop when a given path disappears from the tree.
601</p>
602</dd>
603<dt>
Junio C Hamano7ccb9fd2006-07-15 01:38:40[diff] [blame]604--no-merges
605</dt>
606<dd>
607<p>
608 Do not print commits with more than one parent.
609</p>
610</dd>
611<dt>
Junio C Hamano872c5682006-07-07 06:05:40[diff] [blame]612--not
613</dt>
614<dd>
615<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]616 Reverses the meaning of the <em>^</em> prefix (or lack thereof)
617 for all following revision specifiers, up to the next <em>--not</em>.
Junio C Hamano872c5682006-07-07 06:05:40[diff] [blame]618</p>
619</dd>
620<dt>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]621--all
622</dt>
623<dd>
624<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]625 Pretend as if all the refs in <tt>$GIT_DIR/refs/</tt> are listed on the
626 command line as <em>&lt;commit&gt;</em>.
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]627</p>
628</dd>
Junio C Hamano859f3b42006-08-04 10:04:30[diff] [blame]629<dt>
Junio C Hamanoc9245d92006-09-06 09:35:46[diff] [blame]630--stdin
631</dt>
632<dd>
633<p>
634 In addition to the <em>&lt;commit&gt;</em> listed on the command
635 line, read them from the standard input.
636</p>
637</dd>
638<dt>
Junio C Hamano859f3b42006-08-04 10:04:30[diff] [blame]639--merge
640</dt>
641<dd>
642<p>
643 After a failed merge, show refs that touch files having a
644 conflict and don't exist on all heads to merge.
645</p>
646</dd>
Junio C Hamanoa0778c92006-08-29 04:03:11[diff] [blame]647<dt>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]648--boundary
Junio C Hamanoa0778c92006-08-29 04:03:11[diff] [blame]649</dt>
650<dd>
651<p>
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]652 Output uninteresting commits at the boundary, which are usually
653 not shown.
654</p>
655</dd>
656<dt>
657--dense, --sparse
658</dt>
659<dd>
660<p>
661When optional paths are given, the default behaviour (<em>--dense</em>) is to
662only output commits that changes at least one of them, and also ignore
663merges that do not touch the given paths.
664</p>
665<p>Use the <em>--sparse</em> flag to makes the command output all eligible commits
666(still subject to count and age limitation), but apply merge
667simplification nevertheless.</p>
668</dd>
669<dt>
670--bisect
671</dt>
672<dd>
673<p>
674Limit output to the one commit object which is roughly halfway between
675the included and excluded commits. Thus, if
676</p>
677<div class="listingblock">
678<div class="content">
679<pre><tt> $ git-rev-list --bisect foo ^bar ^baz</tt></pre>
680</div></div>
681<p>outputs <em>midpoint</em>, the output of the two commands</p>
682<div class="listingblock">
683<div class="content">
684<pre><tt> $ git-rev-list foo ^midpoint
685 $ git-rev-list midpoint ^bar ^baz</tt></pre>
686</div></div>
687<p>would be of roughly the same length. Finding the change which
688introduces a regression is thus reduced to a binary search: repeatedly
689generate and test new 'midpoint's until the commit chain is of length
690one.</p>
691</dd>
692</dl>
693<h3>Commit Ordering</h3>
694<p>By default, the commits are shown in reverse chronological order.</p>
695<dl>
696<dt>
697--topo-order
698</dt>
699<dd>
700<p>
701 This option makes them appear in topological order (i.e.
702 descendant commits are shown before their parents).
703</p>
704</dd>
705<dt>
706--date-order
707</dt>
708<dd>
709<p>
710 This option is similar to <em>--topo-order</em> in the sense that no
711 parent comes before all of its children, but otherwise things
712 are still ordered in the commit timestamp order.
713</p>
714</dd>
715</dl>
716<h3>Object Traversal</h3>
717<p>These options are mostly targeted for packing of git repositories.</p>
718<dl>
719<dt>
720--objects
721</dt>
722<dd>
723<p>
724 Print the object IDs of any object referenced by the listed
725 commits. <em>git-rev-list --objects foo ^bar</em> thus means "send me
726 all object IDs which I need to download if I have the commit
727 object <em>bar</em>, but not <em>foo</em>".
728</p>
729</dd>
730<dt>
731--objects-edge
732</dt>
733<dd>
734<p>
735 Similar to <em>--objects</em>, but also print the IDs of excluded
736 commits prefixed with a "-" character. This is used by
737 <a href="git-pack-objects.html">git-pack-objects(1)</a> to build "thin" pack, which records
738 objects in deltified form based on objects contained in these
739 excluded commits to reduce network traffic.
740</p>
741</dd>
742<dt>
743--unpacked
744</dt>
745<dd>
746<p>
747 Only useful with <em>--objects</em>; print the object IDs that are not
748 in packs.
Junio C Hamanoa0778c92006-08-29 04:03:11[diff] [blame]749</p>
750</dd>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]751</dl>
752</div>
753<h2>Author</h2>
754<div class="sectionbody">
755<p>Written by Linus Torvalds &lt;torvalds@osdl.org&gt;</p>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]756</div>
757<h2>Documentation</h2>
758<div class="sectionbody">
Junio C Hamano89e135d2006-09-03 06:18:25[diff] [blame]759<p>Documentation by David Greaves, Junio C Hamano, Jonas Fonseca
760and the git-list &lt;git@vger.kernel.org&gt;.</p>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]761</div>
762<h2>GIT</h2>
763<div class="sectionbody">
764<p>Part of the <a href="git.html">git(7)</a> suite</p>
765</div>
766<div id="footer">
767<div id="footer-text">
Junio C Hamanoa340aaa2006-11-23 02:47:33[diff] [blame]768Last updated 23-Nov-2006 02:47:21 UTC
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]769</div>
770</div>
771</body>
772</html>