<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">\r
<head>\r
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />\r
-<meta name="generator" content="AsciiDoc 7.0.1" />\r
+<meta name="generator" content="AsciiDoc 7.0.2" />\r
<style type="text/css">\r
/* Debug borders */\r
p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {\r
</div>\r
<div id="preamble">\r
<div class="sectionbody">\r
-<p>So you're a CVS user. That's ok, it's a treatable condition. The job of\r
+<p>So you're a CVS user. That's OK, it's a treatable condition. The job of\r
this document is to put you on the road to recovery, by helping you\r
convert an existing cvs repository to git, and by showing you how to use a\r
git repository in a cvs-like fashion.</p>\r
<p>Make sure committers have a umask of at most 027, so that the directories\r
they create are writable and searchable by other group members.</p>\r
<p>Suppose this repository is now set up in /pub/repo.git on the host\r
-foo.com. Then as an individual commiter you can clone the shared\r
+foo.com. Then as an individual committer you can clone the shared\r
repository:</p>\r
<div class="listingblock">\r
<div class="content">\r
<div class="title">Note</div>\r
</td>\r
<td class="content">\r
-<p>Because of this behaviour, if the shared repository and the developer's\r
+<p>Because of this behavior, if the shared repository and the developer's\r
repository both have branches named <tt>origin</tt>, then a push like the above\r
attempts to update the <tt>origin</tt> branch in the shared repository from the\r
developer's <tt>origin</tt> branch. The results may be unexpected, so it's\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 30-Jan-2006 23:10:24 PDT\r
+Last updated 07-Jun-2006 19:51:36 UTC\r
</div>\r
</div>\r
</body>\r
projects / git.git / blobdiff