<div class="sectionbody">\r
<p>You may find these things in your git repository (<tt>.git</tt>\r
directory for a repository associated with your working tree, or\r
-<tt><em>project</em>.git</tt> directory for a public <em>naked</em> repository).</p>\r
+<tt><em>project</em>.git</tt> directory for a public <em>bare</em> repository).</p>\r
<dl>\r
<dt>\r
objects\r
You can be using <tt>objects/info/alternates</tt> mechanism, or\r
<tt>$GIT_ALTERNATE_OBJECT_DIRECTORIES</tt> mechanism to <em>borrow</em>\r
objects from other object stores. A repository with this kind\r
-of incompete object store is not suitable to be published for\r
+of incomplete object store is not suitable to be published for\r
use with dumb transports but otherwise is OK as long as\r
<tt>objects/info/alternates</tt> points at the right object stores\r
it borrows from.\r
A symlink of the form <tt>refs/heads/<em>name</em></tt> to point at\r
the current branch, if exists. It does not mean much if\r
the repository is not associated with any working tree\r
- (i.e. <em>naked</em> repository), but a valid git repository\r
+ (i.e. a <em>bare</em> repository), but a valid git repository\r
<strong>must</strong> have such a symlink here. It is legal if the\r
named branch <em>name</em> does not (yet) exist.\r
</p>\r
<dd>\r
<p>\r
The current index file for the repository. It is\r
- usually not found in a naked repository.\r
+ usually not found in a bare repository.\r
</p>\r
</dd>\r
<dt>\r
up-to-date if the repository is published for dumb\r
transports. The <tt>git-receive-pack</tt> command, which is\r
run on a remote repository when you <tt>git push</tt> into it,\r
- runs <tt>hooks/update</tt> hook to help you achive this.\r
+ runs <tt>hooks/update</tt> hook to help you achieve this.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 27-Dec-2005 00:17:09 PDT\r
+Last updated 25-Jan-2006 04:37:17 PDT\r
</div>\r
</div>\r
</body>\r