Autogenerated HTML docs for v1.6.0.1-141-g445ca

diff --git a/git-diff-tree.html b/git-diff-tree.html
index 58417770856d282749473c580c5a2b68aa556653..c33b89c5d92dd9ca861bcc24f82d304110d9d66f 100644 (file)
--- a/git-diff-tree.html
+++ b/git-diff-tree.html
@@ -1184,7 +1184,7 @@ The title was >>t4119: test autocomputing -p<n> for traditional diff
 </li>\r
 <li>\r
 <p>\r
-<em>%ad</em>: author date\r
+<em>%ad</em>: author date (format respects --date= option)\r
 </p>\r
 </li>\r
 <li>\r
@@ -1862,7 +1862,7 @@ the pathname, but if that is <tt>NUL</tt>, the record will show two paths.</p></
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 2008-08-21 10:34:00 UTC\r
+Last updated 2008-08-29 08:56:28 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-log.html b/git-log.html
index 6d7ecdf32490b10bc704b2995299f7f712f2e9c8..cfd046a23f3616ef53f03bcbf5ec62543c96272d 100644 (file)
--- a/git-log.html
+++ b/git-log.html
@@ -1698,7 +1698,7 @@ The title was >>t4119: test autocomputing -p<n> for traditional diff
 </li>\r
 <li>\r
 <p>\r
-<em>%ad</em>: author date\r
+<em>%ad</em>: author date (format respects --date= option)\r
 </p>\r
 </li>\r
 <li>\r
@@ -2166,7 +2166,7 @@ reversible operation.</p></div>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 2008-08-20 09:13:33 UTC\r
+Last updated 2008-08-29 08:56:28 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-rev-list.html b/git-rev-list.html
index 3955a0b18e16bcb424dfc463a10f82137e40101a..e9af4092f2c9af7d8f18b85c58fd2931efcaa2e3 100644 (file)
--- a/git-rev-list.html
+++ b/git-rev-list.html
@@ -1285,7 +1285,7 @@ The title was >>t4119: test autocomputing -p<n> for traditional diff
 </li>\r
 <li>\r
 <p>\r
-<em>%ad</em>: author date\r
+<em>%ad</em>: author date (format respects --date= option)\r
 </p>\r
 </li>\r
 <li>\r
@@ -1441,7 +1441,7 @@ and the git-list &lt;git@vger.kernel.org&gt;.</p></div>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 2008-08-13 20:03:49 UTC\r
+Last updated 2008-08-29 08:56:30 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-show.html b/git-show.html
index 735cbe21427d9230526efc95948794631f9eb9f5..9ffdb11008dfcf16aca5437bc2b28b9f65bbb442 100644 (file)
--- a/git-show.html
+++ b/git-show.html
@@ -577,7 +577,7 @@ The title was >>t4119: test autocomputing -p<n> for traditional diff
 </li>\r
 <li>\r
 <p>\r
-<em>%ad</em>: author date\r
+<em>%ad</em>: author date (format respects --date= option)\r
 </p>\r
 </li>\r
 <li>\r
@@ -850,7 +850,7 @@ Johannes Schindelin &lt;Johannes.Schindelin@gmx.de&gt;.</p></div>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 2008-07-31 22:10:23 UTC\r
+Last updated 2008-08-29 08:56:30 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-whatchanged.html b/git-whatchanged.html
index 3f845e7208214985b17372654fa523261f554c22..30270517f32fca8994a9fcbb3c57855feda0e61e 100644 (file)
--- a/git-whatchanged.html
+++ b/git-whatchanged.html
@@ -609,7 +609,7 @@ The title was >>t4119: test autocomputing -p<n> for traditional diff
 </li>\r
 <li>\r
 <p>\r
-<em>%ad</em>: author date\r
+<em>%ad</em>: author date (format respects --date= option)\r
 </p>\r
 </li>\r
 <li>\r
@@ -789,7 +789,7 @@ Junio C Hamano &lt;gitster@pobox.com&gt;</p></div>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 2008-07-22 09:19:18 UTC\r
+Last updated 2008-08-29 08:56:31 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/gitk.html b/gitk.html
index e172903ea5604804f13e958687fcf1a07948ef76..75ad617f337dbbd739c07ef6d61bd49e84431a03 100644 (file)
--- a/gitk.html
+++ b/gitk.html
@@ -384,6 +384,18 @@ frequently used options.</p></div>
 </p>\r
 </dd>\r
 <dt>\r
+--argscmd=&lt;command&gt;\r
+</dt>\r
+<dd>\r
+<p>\r
+        Command to be run each time gitk has to determine the list of\r
+        &lt;revs&gt; to show.  The command is expected to print on its standard\r
+        output a list of additional revs to be shown, one per line.\r
+        Use this instead of explicitly specifying &lt;revs&gt; if the set of\r
+        commits to show may vary between refreshes.\r
+</p>\r
+</dd>\r
+<dt>\r
 &lt;revs&gt;\r
 </dt>\r
 <dd>\r
@@ -492,7 +504,7 @@ such as display options, font, and colors.</p></div>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 2008-07-31 22:10:25 UTC\r
+Last updated 2008-08-29 08:56:32 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/gitk.txt b/gitk.txt
index 6e827cd11c6d464e1369bf1ca23af0dd53b9be32..ae29a00d591289b0b2534402599fa7a6fe1e3266 100644 (file)
--- a/gitk.txt
+++ b/gitk.txt
@@ -49,6 +49,13 @@ frequently used options.
        the history between two branches (i.e. the HEAD and the MERGE_HEAD)
        that modify the conflicted files.
 
+--argscmd=<command>::
+       Command to be run each time gitk has to determine the list of
+       <revs> to show.  The command is expected to print on its standard
+       output a list of additional revs to be shown, one per line.
+       Use this instead of explicitly specifying <revs> if the set of
+       commits to show may vary between refreshes.
+
 <revs>::
 
        Limit the revisions to show. This can be either a single revision

diff --git a/gittutorial.html b/gittutorial.html
index 8651c5bc68301914425424cb3a53d2eb6034de5d..6e616900def04272a3566eebff98a6a58e1fa3dd 100644 (file)
--- a/gittutorial.html
+++ b/gittutorial.html
@@ -586,9 +586,31 @@ pulling, like this:</p></div>
 <div class="listingblock">\r
 <div class="content">\r
 <pre><tt>alice$ git fetch /home/bob/myrepo master\r
-alice$ git log -p ..FETCH_HEAD</tt></pre>\r
+alice$ git log -p HEAD..FETCH_HEAD</tt></pre>\r
 </div></div>\r
-<div class="para"><p>This operation is safe even if Alice has uncommitted local changes.</p></div>\r
+<div class="para"><p>This operation is safe even if Alice has uncommitted local changes.\r
+The range notation HEAD..FETCH_HEAD" means "show everything that is reachable\r
+from the FETCH_HEAD but exclude anything that is reachable from HEAD.\r
+Alice already knows everything that leads to her current state (HEAD),\r
+and reviewing what Bob has in his state (FETCH_HEAD) that she has not\r
+seen with this command</p></div>\r
+<div class="para"><p>If Alice wants to visualize what Bob did since their histories forked\r
+she can issue the following command:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>$ gitk HEAD..FETCH_HEAD</tt></pre>\r
+</div></div>\r
+<div class="para"><p>This uses the same two-dot range notation we saw earlier with <em>git log</em>.</p></div>\r
+<div class="para"><p>Alice may want to view what both of them did since they forked.\r
+She can use three-dot form instead of the two-dot form:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>$ gitk HEAD...FETCH_HEAD</tt></pre>\r
+</div></div>\r
+<div class="para"><p>This means "show everything that is reachable from either one, but\r
+exclude anything that is reachable from both of them".</p></div>\r
+<div class="para"><p>Please note that these range notation can be used with both gitk\r
+and "git log".</p></div>\r
 <div class="para"><p>After inspecting what Bob did, if there is nothing urgent, Alice may\r
 decide to continue working without pulling from Bob.  If Bob's history\r
 does have something Alice would immediately need, Alice may choose to\r
@@ -881,7 +903,7 @@ digressions that may be interesting at this point are:</p></div>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 2008-07-15 15:48:35 UTC\r
+Last updated 2008-08-29 08:56:32 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/gittutorial.txt b/gittutorial.txt
index 48d1454a90cf9453e5e3c9fa01b3dbc369a58f1f..384972cb9bb4a04c55bd8c4796bcd3408e44d5e9 100644 (file)
--- a/gittutorial.txt
+++ b/gittutorial.txt
@@ -321,10 +321,37 @@ pulling, like this:
 
 ------------------------------------------------
 alice$ git fetch /home/bob/myrepo master
-alice$ git log -p ..FETCH_HEAD
+alice$ git log -p HEAD..FETCH_HEAD
 ------------------------------------------------
 
 This operation is safe even if Alice has uncommitted local changes.
+The range notation HEAD..FETCH_HEAD" means "show everything that is reachable
+from the FETCH_HEAD but exclude anything that is reachable from HEAD.
+Alice already knows everything that leads to her current state (HEAD),
+and reviewing what Bob has in his state (FETCH_HEAD) that she has not
+seen with this command
+
+If Alice wants to visualize what Bob did since their histories forked
+she can issue the following command:
+
+------------------------------------------------
+$ gitk HEAD..FETCH_HEAD
+------------------------------------------------
+
+This uses the same two-dot range notation we saw earlier with 'git log'.
+
+Alice may want to view what both of them did since they forked.
+She can use three-dot form instead of the two-dot form:
+
+------------------------------------------------
+$ gitk HEAD...FETCH_HEAD
+------------------------------------------------
+
+This means "show everything that is reachable from either one, but
+exclude anything that is reachable from both of them".
+
+Please note that these range notation can be used with both gitk
+and "git log".
 
 After inspecting what Bob did, if there is nothing urgent, Alice may
 decide to continue working without pulling from Bob.  If Bob's history

diff --git a/pretty-formats.txt b/pretty-formats.txt
index c11d4957714db202a012209e2437b9e050a28ae0..388d4925e6bc4bacb708f75437e9aaa216fcb9cc 100644 (file)
--- a/pretty-formats.txt
+++ b/pretty-formats.txt
@@ -103,7 +103,7 @@ The placeholders are:
 - '%an': author name
 - '%aN': author name (respecting .mailmap)
 - '%ae': author email
-- '%ad': author date
+- '%ad': author date (format respects --date= option)
 - '%aD': author date, RFC2822 style
 - '%ar': author date, relative
 - '%at': author date, UNIX timestamp