Autogenerated HTML docs for v1.8.1.2-545-g2f19ad

1 files changed, 12 insertions, 12 deletions

diff --git a/git-bisect-lk2009.html b/git-bisect-lk2009.html
index b7b131bad..6763f0399 100644
--- a/git-bisect-lk2009.html
+++ b/git-bisect-lk2009.html
@@ -941,7 +941,7 @@ Bisecting: 10928 revisions left to test after this (roughly 14 steps)
 will be looking for the first commit that has a version like

 "2.6.26-something", that is the commit that has a "SUBLEVEL = 26" line

 in the top level Makefile. This is a toy example because there are

-better ways to find this commit with git than using "git bisect" (for

+better ways to find this commit with Git than using "git bisect" (for

 example "git blame" or "git log -S&lt;string&gt;").</p></div>

 </div>

 <div class="sect2">

@@ -1148,7 +1148,7 @@ W---W</code></pre>
 <div class="paragraph"><p>So only the W and B commits will be kept. Because commits X and Y will

 have been removed by rules a) and b) respectively, and because commits

 G are removed by rule b) too.</p></div>

-<div class="paragraph"><p>Note for git users, that it is equivalent as keeping only the commit

+<div class="paragraph"><p>Note for Git users, that it is equivalent as keeping only the commit

 given by:</p></div>

 <div class="listingblock">

 <div class="content">

@@ -1360,8 +1360,8 @@ to get an index into this list</p></div>
 <div class="paragraph"><p>After step 7) (in the skip algorithm), we could check if the second

 commit has been skipped and return it if it is not the case. And in

 fact that was the algorithm we used from when "git bisect skip" was

-developed in git version 1.5.4 (released on February 1st 2008) until

-git version 1.6.4 (released July 29th 2009).</p></div>

+developed in Git version 1.5.4 (released on February 1st 2008) until

+Git version 1.6.4 (released July 29th 2009).</p></div>

 <div class="paragraph"><p>But Ingo Molnar and H. Peter Anvin (another well known linux kernel

 developer) both complained that sometimes the best bisection points

 all happened to be in an area where all the commits are

@@ -1640,10 +1640,10 @@ commit both the fix and the test script (and if needed more tests)
 <div class="content">

 <div class="paragraph"><p>To give some hard figures, we used to have an average report-to-fix

 cycle of 142.6 hours (according to our somewhat weird bug-tracker

-which just measures wall-clock time). Since we moved to git, we&#8217;ve

+which just measures wall-clock time). Since we moved to Git, we&#8217;ve

 lowered that to 16.2 hours. Primarily because we can stay on top of

 the bug fixing now, and because everyone&#8217;s jockeying to get to fix

-bugs (we&#8217;re quite proud of how lazy we are to let git find the bugs

+bugs (we&#8217;re quite proud of how lazy we are to let Git find the bugs

 for us). Each new release results in ~40% fewer bugs (almost certainly

 due to how we now feel about writing tests).</p></div>

 </div>

@@ -1816,9 +1816,9 @@ automatically be shared like branches or tags among developers.</p></div>
 commits in already released history, for example to change the commit

 message or the author. And it can also be used instead of git "grafts"

 to link a repository with another old repository.</p></div>

-<div class="paragraph"><p>In fact it&#8217;s this last feature that "sold" it to the git community, so

-it is now in the "master" branch of git&#8217;s git repository and it should

-be released in git 1.6.5 in October or November 2009.</p></div>

+<div class="paragraph"><p>In fact it&#8217;s this last feature that "sold" it to the Git community, so

+it is now in the "master" branch of Git&#8217;s Git repository and it should

+be released in Git 1.6.5 in October or November 2009.</p></div>

 <div class="paragraph"><p>One problem with "git replace" is that currently it stores all the

 replacements refs in "refs/replace/", but it would be perhaps better

 if the replacement refs that are useful only for bisecting would be in

@@ -1906,7 +1906,7 @@ layout dependent.</p></div>
 <h2 id="_acknowledgements">Acknowledgements</h2>

 <div class="sectionbody">

 <div class="paragraph"><p>Many thanks to Junio Hamano for his help in reviewing this paper, for

-reviewing the patches I sent to the git mailing list, for discussing

+reviewing the patches I sent to the Git mailing list, for discussing

 some ideas and helping me improve them, for improving "git bisect" a

 lot and for his awesome work in maintaining and developing Git.</p></div>

 <div class="paragraph"><p>Many thanks to Ingo Molnar for giving me very useful information that

@@ -1916,7 +1916,7 @@ on the linux kernel mailing lists.</p></div>
 <div class="paragraph"><p>Many thanks to Linus Torvalds for inventing, developing and

 evangelizing "git bisect", Git and Linux.</p></div>

 <div class="paragraph"><p>Many thanks to the many other great people who helped one way or

-another when I worked on git, especially to Andreas Ericsson, Johannes

+another when I worked on Git, especially to Andreas Ericsson, Johannes

 Schindelin, H. Peter Anvin, Daniel Barkalow, Bill Lear, John Hawley,

 Shawn O. Pierce, Jeff King, Sam Vilain, Jon Seymour.</p></div>

 <div class="paragraph"><p>Many thanks to the Linux-Kongress program committee for choosing the

@@ -1979,7 +1979,7 @@ author to given a talk and for publishing this paper.</p></div>
 <div id="footnotes"><hr /></div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2012-11-20 13:06:02 PST

+Last updated 2013-02-05 21:07:26 PST

 </div>

 </div>

 </body>