Autogenerated HTML docs for v1.6.3.2-306-g4f4fa

1 files changed, 33 insertions, 34 deletions

diff --git a/git-rerere.html b/git-rerere.html
index 6c4b14789..e6cd3dbbf 100644
--- a/git-rerere.html
+++ b/git-rerere.html
@@ -324,14 +324,14 @@ git-rerere(1) Manual Page
 </div>

 <h2 id="_description">DESCRIPTION</h2>

 <div class="sectionbody">

-<div class="para"><p>In a workflow that employs relatively long lived topic branches,

-the developer sometimes needs to resolve the same conflict over

+<div class="para"><p>In a workflow employing relatively long lived topic branches,

+the developer sometimes needs to resolve the same conflicts over

 and over again until the topic branches are done (either merged

 to the "release" branch, or sent out and accepted upstream).</p></div>

-<div class="para"><p>This command helps this process by recording conflicted

-automerge results and corresponding hand-resolve results on the

-initial manual merge, and later by noticing the same automerge

-results and applying the previously recorded hand resolution.</p></div>

+<div class="para"><p>This command assists the developer in this process by recording

+conflicted automerge results and corresponding hand resolve results

+on the initial manual merge, and applying previously recorded

+hand resolutions to their corresponding automerge results.</p></div>

 <div class="admonitionblock">

 <table><tr>

 <td class="icon">

@@ -383,19 +383,19 @@ for resolutions.
 </dt>

 <dd>

 <p>

-This command is used to prune records of conflicted merge that

-occurred long time ago.  By default, conflicts older than 15

-days that you have not recorded their resolution, and conflicts

-older than 60 days, are pruned.  These are controlled with

+This prunes records of conflicted merges that

+occurred a long time ago.  By default, unresolved conflicts older

+than 15 days and resolved conflicts older than 60

+days are pruned.  These defaults are controlled via the

 <tt>gc.rerereunresolved</tt> and <tt>gc.rerereresolved</tt> configuration

-variables.

+variables respectively.

 </p>

 </dd>

 </dl></div>

 </div>

 <h2 id="_discussion">DISCUSSION</h2>

 <div class="sectionbody">

-<div class="para"><p>When your topic branch modifies overlapping area that your

+<div class="para"><p>When your topic branch modifies an overlapping area that your

 master branch (or upstream) touched since your topic branch

 forked from it, you may want to test it with the latest master,

 even before your topic branch is ready to be pushed upstream:</p></div>

@@ -464,39 +464,38 @@ top of the tip before the test merge:</p></div>
 <div class="para"><p>This would leave only one merge commit when your topic branch is

 finally ready and merged into the master branch.  This merge

 would require you to resolve the conflict, introduced by the

-commits marked with <tt>*</tt>.  However, often this conflict is the

+commits marked with <tt>*</tt>.  However, this conflict is often the

 same conflict you resolved when you created the test merge you

-blew away.  <em>git-rerere</em> command helps you to resolve this final

+blew away.  <em>git-rerere</em> helps you resolve this final

 conflicted merge using the information from your earlier hand

 resolve.</p></div>

 <div class="para"><p>Running the <em>git-rerere</em> command immediately after a conflicted

 automerge records the conflicted working tree files, with the

 usual conflict markers <tt>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</tt>, <tt>=======</tt>, and <tt>&gt;&gt;&gt;&gt;&gt;&gt;&gt;</tt> in

 them.  Later, after you are done resolving the conflicts,

-running <em>git-rerere</em> again records the resolved state of these

+running <em>git-rerere</em> again will record the resolved state of these

 files.  Suppose you did this when you created the test merge of

 master into the topic branch.</p></div>

-<div class="para"><p>Next time, running <em>git-rerere</em> after seeing a conflicted

-automerge, if the conflict is the same as the earlier one

-recorded, it is noticed and a three-way merge between the

+<div class="para"><p>Next time, after seeing the same conflicted automerge,

+running <em>git-rerere</em> will perform a three-way merge between the

 earlier conflicted automerge, the earlier manual resolution, and

-the current conflicted automerge is performed by the command.

+the current conflicted automerge.

 If this three-way merge resolves cleanly, the result is written

-out to your working tree file, so you would not have to manually

+out to your working tree file, so you do not have to manually

 resolve it.  Note that <em>git-rerere</em> leaves the index file alone,

 so you still need to do the final sanity checks with <tt>git diff</tt>

 (or <tt>git diff -c</tt>) and <em>git-add</em> when you are satisfied.</p></div>

 <div class="para"><p>As a convenience measure, <em>git-merge</em> automatically invokes

-<em>git-rerere</em> when it exits with a failed automerge, which

-records it if it is a new conflict, or reuses the earlier hand

+<em>git-rerere</em> upon exiting with a failed automerge and <em>git-rerere</em>

+records the hand resolve when it is a new conflict, or reuses the earlier hand

 resolve when it is not.  <em>git-commit</em> also invokes <em>git-rerere</em>

-when recording a merge result.  What this means is that you do

-not have to do anything special yourself (Note: you still have

-to set the config variable rerere.enabled to enable this command).</p></div>

-<div class="para"><p>In our example, when you did the test merge, the manual

+when committing a merge result.  What this means is that you do

+not have to do anything special yourself (besides enabling

+the rerere.enabled config variable).</p></div>

+<div class="para"><p>In our example, when you do the test merge, the manual

 resolution is recorded, and it will be reused when you do the

-actual merge later with updated master and topic branch, as long

-as the earlier resolution is still applicable.</p></div>

+actual merge later with the updated master and topic branch, as long

+as the recorded resolution is still applicable.</p></div>

 <div class="para"><p>The information <em>git-rerere</em> records is also used when running

 <em>git-rebase</em>.  After blowing away the test merge and continuing

 development on the topic branch:</p></div>

@@ -512,11 +511,11 @@ development on the topic branch:</p></div>
                                  /

     o---o---o---*---o---o---o---o   master</tt></pre>

 </div></div>

-<div class="para"><p>you could run <tt>git rebase master topic</tt>, to keep yourself

-up-to-date even before your topic is ready to be sent upstream.

-This would result in falling back to three-way merge, and it

-would conflict the same way the test merge you resolved earlier.

-<em>git-rerere</em> is run by <em>git-rebase</em> to help you resolve this

+<div class="para"><p>you could run <tt>git rebase master topic</tt>, to bring yourself

+up-to-date before your topic is ready to be sent upstream.

+This would result in falling back to a three-way merge, and it

+would conflict the same way as the test merge you resolved earlier.

+<em>git-rerere</em> will be run by <em>git-rebase</em> to help you resolve this

 conflict.</p></div>

 </div>

 <h2 id="_author">Author</h2>

@@ -529,7 +528,7 @@ conflict.</p></div>
 </div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2009-04-02 06:50:02 UTC

+Last updated 2009-06-14 01:03:01 UTC

 </div>

 </div>

 </body>