Autogenerated HTML docs for v1.7.0.4-360-g1176

1 files changed, 12 insertions, 84 deletions

diff --git a/everyday.html b/everyday.html
index af1c62820..7f3e15de2 100644
--- a/everyday.html
+++ b/everyday.html
@@ -311,12 +311,8 @@ div#toc a:visited { color: blue; }
 </div>

 <div id="preamble">

 <div class="sectionbody">

-<div class="para"><p><a href="#Basic Repository">[Basic Repository]</a> commands are needed by people who have a

-repository --- that is everybody, because every working tree of

-git is a repository.</p></div>

-<div class="para"><p>In addition, <a href="#Individual Developer (Standalone)">[Individual Developer (Standalone)]</a> commands are

-essential for anybody who makes a commit, even for somebody who

-works alone.</p></div>

+<div class="para"><p><a href="#Individual Developer (Standalone)">[Individual Developer (Standalone)]</a> commands are essential for

+anybody who makes a commit, even for somebody who works alone.</p></div>

 <div class="para"><p>If you work with other people, you will need commands listed in

 the <a href="#Individual Developer (Participant)">[Individual Developer (Participant)]</a> section as well.</p></div>

 <div class="para"><p>People who play the <a href="#Integrator">[Integrator]</a> role need to learn some more

@@ -326,79 +322,6 @@ administrators who are responsible for the care and feeding
 of git repositories.</p></div>

 </div>

 </div>

-<h2 id="_basic_repository_a_id_basic_repository_a">Basic Repository<a id="Basic Repository"></a></h2>

-<div class="sectionbody">

-<div class="para"><p>Everybody uses these commands to maintain git repositories.</p></div>

-<div class="ilist"><ul>

-<li>

-<p>

-<a href="git-init.html">git-init(1)</a> or <a href="git-clone.html">git-clone(1)</a> to create a

-    new repository.

-</p>

-</li>

-<li>

-<p>

-<a href="git-fsck.html">git-fsck(1)</a> to check the repository for errors.

-</p>

-</li>

-<li>

-<p>

-<a href="git-gc.html">git-gc(1)</a> to do common housekeeping tasks such as

-    repack and prune.

-</p>

-</li>

-</ul></div>

-<h3 id="_examples">Examples</h3><div style="clear:left"></div>

-<div class="vlist"><dl>

-<dt>

-Check health and remove cruft.

-</dt>

-<dd>

-<div class="listingblock">

-<div class="content">

-<pre><tt>$ git fsck <b>(1)</b>

-$ git count-objects <b>(2)</b>

-$ git gc <b>(3)</b></tt></pre>

-</div></div>

-<div class="colist"><ol>

-<li>

-<p>

-running without <tt>--full</tt> is usually cheap and assures the

-repository health reasonably well.

-</p>

-</li>

-<li>

-<p>

-check how many loose objects there are and how much

-disk space is wasted by not repacking.

-</p>

-</li>

-<li>

-<p>

-repacks the local repository and performs other housekeeping tasks.

-</p>

-</li>

-</ol></div>

-</dd>

-<dt>

-Repack a small project into single pack.

-</dt>

-<dd>

-<div class="listingblock">

-<div class="content">

-<pre><tt>$ git gc <b>(1)</b></tt></pre>

-</div></div>

-<div class="colist"><ol>

-<li>

-<p>

-pack all the objects reachable from the refs into one pack,

-then remove the other packs.

-</p>

-</li>

-</ol></div>

-</dd>

-</dl></div>

-</div>

 <h2 id="_individual_developer_standalone_a_id_individual_developer_standalone_a">Individual Developer (Standalone)<a id="Individual Developer (Standalone)"></a></h2>

 <div class="sectionbody">

 <div class="para"><p>A standalone individual developer does not exchange patches with

@@ -407,6 +330,11 @@ following commands.</p></div>
 <div class="ilist"><ul>

 <li>

 <p>

+<a href="git-init.html">git-init(1)</a> to create a new repository.

+</p>

+</li>

+<li>

+<p>

 <a href="git-show-branch.html">git-show-branch(1)</a> to see where you are.

 </p>

 </li>

@@ -459,7 +387,7 @@ following commands.</p></div>
 </p>

 </li>

 </ul></div>

-<h3 id="_examples_2">Examples</h3><div style="clear:left"></div>

+<h3 id="_examples">Examples</h3><div style="clear:left"></div>

 <div class="vlist"><dl>

 <dt>

 Use a tarball as a starting point for a new repository.

@@ -611,7 +539,7 @@ addition to the ones needed by a standalone developer.</p></div>
 </p>

 </li>

 </ul></div>

-<h3 id="_examples_3">Examples</h3><div style="clear:left"></div>

+<h3 id="_examples_2">Examples</h3><div style="clear:left"></div>

 <div class="vlist"><dl>

 <dt>

 Clone the upstream and work on it.  Feed changes to upstream.

@@ -799,7 +727,7 @@ commands in addition to the ones needed by participants.</p></div>
 </p>

 </li>

 </ul></div>

-<h3 id="_examples_4">Examples</h3><div style="clear:left"></div>

+<h3 id="_examples_3">Examples</h3><div style="clear:left"></div>

 <div class="vlist"><dl>

 <dt>

 My typical GIT day.

@@ -939,7 +867,7 @@ and maintain access to the repository by developers.</p></div>
 </ul></div>

 <div class="para"><p><a href="howto/update-hook-example.txt">update hook howto</a> has a good

 example of managing a shared central repository.</p></div>

-<h3 id="_examples_5">Examples</h3><div style="clear:left"></div>

+<h3 id="_examples_4">Examples</h3><div style="clear:left"></div>

 <div class="vlist"><dl>

 <dt>

 We assume the following in /etc/services

@@ -1098,7 +1026,7 @@ upload to public HTTP server hosted by your ISP.
 </div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2010-02-13 01:00:05 UTC

+Last updated 2010-04-04 19:11:47 UTC

 </div>

 </div>

 </body>