----- Original Message ----- > From: "Stuart Henderson" <s...@spacehopper.org> > To: "misc" <misc@openbsd.org> > Sent: Saturday, September 12, 2015 11:58:29 AM > Subject: Re: anoncvs.html.head
> On 2015-09-11, Rob Pierce <r...@2keys.ca> wrote: >> <li><b>src</b> - Houses all source code for the OpenBSD Operating System. >> <li><b>ports</b> - Houses the <a href="faq/ports/index.html">OpenBSD >> Ports</a>. >> - <li><b>www</b> - Houses all OpenBSD web pages. (Including this one). >> + <li><b>www</b> - Houses all OpenBSD web pages (including this one). > > I like that > >> <li><b>xenocara</b> - Houses OpenBSD's active X.org v7 source tree. >> <li><b>X11</b> and <b>XF4</b> - Houses OpenBSD's adaptation of the >> <a href="http://www.XFree86.org/";>XFree86-3</a> and XFree86-4 >> @@ -122,7 +122,7 @@ with only one part of the tree. The two >> which contains the files used to create the kernel, and <tt>src.tar.gz</tt> >> which contains all the other "userland" utilities. >> In general, however, you will usually want both of them installed. >> -Assuming the downloaded files, <tt>src.tar.gz</tt>, >> +Assuming the downloaded files <tt>src.tar.gz</tt>, >> <tt>sys.tar.gz</tt> and <tt>xenocara.tar.gz</tt> are in <tt>/usr</tt>: > > I think this was OK as it was > >> <p> >> -Not all people will wish to unpack all the file sets, but as the system >> +Not all people will wish to unpack all the source file, but as the system >> must be kept in sync, you will generally need to set up all trees. > > and this (and the new sentence doesn't quite make sense) > >> <p> >> -You can also just use cvs(1) to "<b>checkout</b>" the source repository >> +You can also just use >> +<a >> href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&sektion=1&format=html";>cvs(1)</a> >> +to "<b>checkout</b>" the source repository >> for you. This is discussed in the <a href="#using">next section</a>. > > OK I guess, though I don't think we need to hyperlink every instance of > a program name > >> @@ -160,16 +162,12 @@ from the <a href="errata.html">errata</a >> For more information on these "flavors" of OpenBSD, see >> <a href="faq/faq5.html#Flavors">here</a>. >> >> -<p>Once you have decided which tree to follow, you must choose which >> Anonymous >> -CVS server you are going to use. A list of these servers is >> -<a href="#CVSROOT">below</a>. >> - >> <p> >> -Once you have chosen which <a href="#CVSROOT">Anonymous CVS Server</a> you >> will >> -use, you can start using cvs. For those of you >> +Once you have decided which tree to follow, and which <a >> href="#CVSROOT">Anonymous CVS Server</a> you will > > Please try and keep <80 columns in the source file where sensible > >> +use, you can start using <a >> href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&sektion=1&format=html";>cvs(1)</a>. >> For those of you >> who have CDs you can start with the CVS checkout that is on the CD by using >> the method <a href="#starting">above</a> to get the sources onto your >> system. >> -If you don't have a CD handy, use the method below to checkout the sources. >> +If you don't have a CD handy, use the method below to checkout the sources: >> >> <p> >> <ul><li>First, start out by `get'-ing an initial tree: >> @@ -210,9 +208,11 @@ Confirm this, and the fingerprint will t >> ... >> </pre> >> >> +<p> >> Note that the above format with SHA256 fingerprints was added after the >> release of OpenBSD 5.6; older versions only use MD5 fingerprints. >> >> +<p> >> <li> Anytime afterwards, to `update' this tree: >> <p> (If you are following <i>current</i>): >> <pre> >> @@ -234,7 +234,7 @@ to merge changes in. >> <li> NOTE: >> If you are updating a source tree that you initially fetched >> from a different server, or from a CD, you <strong>must</strong> >> -add the <em>-d [cvsroot]</em> option to cvs. >> +add the <em>-d [cvsroot]</em> option to cvs: >> <pre> >> # <strong>cd /usr/src</strong> >> # <strong>cvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd</strong> >> @@ -295,11 +295,11 @@ directory, and a subsequent update will >> >> <p> >> The anoncvs service gives fledgling developers a chance to learn CVS >> -operation and get thoroughly involved in the development process >> +operations and get thoroughly involved in the development process > > "operation" already seem ok > >> before getting "commit" access -- as a result of showing useful >> skills and high quality results they will naturally later be given >> developer access. >> -As well, people providing patches can create their "diff"s relative >> +As well, people providing patches can create their diffs relative >> to the CVS tree, which will ease integration. >> > > <h3><a name="EXAMPLE"><font color="#0000e0">Example usages for cvs(1)</font> Thanks Stuart. I am preparing a new diff which I will send shortly.
