From 18ab4ada5dfb03bc302610f86a4612506e81be51 Mon Sep 17 00:00:00 2001
From: Hidetoshi Shimokawa <simokawa@FreeBSD.org>
Date: Thu, 11 Feb 1999 04:14:46 +0000
Subject: [PATCH] - Capitalize '-release', '-stable' and '-current'. -
 'ports-current' in ftp sites has moved to 'ports/ports-current'. - Fix typo.

Reviewed by:	asami
---
 handbook/porting.sgml | 40 ++++++++++++++++++++--------------------
 1 file changed, 20 insertions(+), 20 deletions(-)

diff --git a/handbook/porting.sgml b/handbook/porting.sgml
index bac8c73fde..f8ecf0734b 100644
--- a/handbook/porting.sgml
+++ b/handbook/porting.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: porting.sgml,v 1.129 1999-02-08 21:57:59 billf Exp $ -->
+<!-- $Id: porting.sgml,v 1.130 1999-02-11 04:14:46 simokawa Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>Making a port yourself<label id="porting"></heading>
@@ -901,7 +901,7 @@ lib/libtcl80.so.1
 	<sect2>
 	  <heading>ELF support</heading>
 
-	  <p>Since FreeBSD moved to ELF with the 3.0-release,
+	  <p>Since FreeBSD moved to ELF with the 3.0-RELEASE,
 	    we need to convert many ports that build shared libraries
 	    to support ELF.  Complicating this task is that a 3.0
 	    system can run as both ELF and a.out, and we wish to unoffically 
@@ -922,7 +922,7 @@ lib/libtcl80.so.1
 	      <tt>/usr/local/lib</tt> and similar to an `<tt/aout/'
 	      subdirectory.  (If you don't move them out of the way,
 	      ELF ports will happily overwrite a.out libraries.)  The
-	      `<tt/move-aout-libs/' target in the -current
+	      `<tt/move-aout-libs/' target in the 3.0-CURRENT
 	      <tt>src/Makefile</tt> (called from `<tt/aout-to-elf'/)
 	      will do this for you.  It will only move a.out libs so
 	      it is safe to call it on a system with both ELF and
@@ -952,7 +952,7 @@ lib/libtcl80.so.1
 	      `<tt/aout/' or `<tt/elf/' and export it in the
 	      environments <tt/CONFIGURE_ENV/, <tt/SCRIPTS_ENV/ and
 	      <tt/MAKE_ENV/. (It's always going to be `<tt/aout/' in
-	      -stable).  It is also passed to <tt/PLIST_SUB/ as
+	      2.2-STABLE).  It is also passed to <tt/PLIST_SUB/ as
 	      `<tt>PORTOBJFORMAT=${PORTOBJFORMAT}</tt>'.  (See comment 
 	      on <tt/ldconfig/ lines below.)
 
@@ -1592,7 +1592,7 @@ PLIST_SUB=	OCTAVE_VERSION=${OCTAVE_VERSION}
 	  id="porting:pkgsubdir"></heading>
 	<p>All the filenames in the <tt/pkg/ subdirectory are defined
 	  using variables so you can change them in your Makefile if
-	  need be.  This is expecially useful when you are sharing the
+	  need be.  This is especially useful when you are sharing the
 	  same <tt/pkg/ subdirectory among several ports or have to
 	  write to one of the above files (see <ref
 	  id="porting:wrkdir" name="writing to places other than
@@ -1669,7 +1669,7 @@ PKGMESSAGE       ${PKGDIR}/MESSAGE
       <p>When you notice that a port is out of date compared to the
 	latest version from the original authors, first make sure you
 	have the latest port.  You can find them in the
-	<tt>ports-current</tt> directory of the ftp mirror sites.
+	<tt>ports/ports-current</tt> directory of the ftp mirror sites.
 
       <p>The next step is to send a mail to the maintainer, if one is
 	listed in the port's Makefile.  That person may already be
@@ -1873,13 +1873,13 @@ PKGMESSAGE       ${PKGDIR}/MESSAGE
 <tt>__FreeBSD_version</tt> values:
 <tscreen><verb>
 2.0-RELEASE:                    	199411
-2.1-current's:                  	199501, 199503
+2.1-CURRENT's:                  	199501, 199503
 2.0.5-RELEASE:                  	199504
-2.2-current before 2.1:         	199508
+2.2-CURRENT before 2.1:         	199508
 2.1.0-RELEASE:                  	199511
-2.2-current before 2.1.5:       	199512
+2.2-CURRENT before 2.1.5:       	199512
 2.1.5-RELEASE:                  	199607
-2.2-current before 2.1.6:       	199608
+2.2-CURRENT before 2.1.6:       	199608
 2.1.6-RELEASE:                  	199612
 2.1.7-RELEASE:                  	199612
 2.2-RELEASE:                    	220000
@@ -1898,17 +1898,17 @@ PKGMESSAGE       ${PKGDIR}/MESSAGE
 2.2-STABLE after semctl(2) change:     	227002
 2.2.8-RELEASE:                          228000
 2.2-STABLE after 2.2.8-RELEASE:         228001
-3.0-current before mount(2) change:	300000
-3.0-current after mount(2) change:	300001
-3.0-current after semctl(2) change:    	300002
-3.0-current after ioctl arg changes:	300003
-3.0-current after ELF conversion:     	300004
+3.0-CURRENT before mount(2) change:	300000
+3.0-CURRENT after mount(2) change:	300001
+3.0-CURRENT after semctl(2) change:    	300002
+3.0-CURRENT after ioctl arg changes:	300003
+3.0-CURRENT after ELF conversion:     	300004
 3.0-RELEASE: 			    	300005
-3.0-current after 3.0-RELEASE:     	300006
-3.0-stable after 3/4 branch:            300007
+3.0-CURRENT after 3.0-RELEASE:     	300006
+3.0-STABLE after 3/4 branch:            300007
 3.1-RELEASE:				310000
-3.1-stable after 3.1-RELEASE:		310001
-4.0-current after 3/4 branch:           400000
+3.1-STABLE after 3.1-RELEASE:		310001
+4.0-CURRENT after 3/4 branch:           400000
 </verb></tscreen>
 	  (Note that 2.2-STABLE sometimes identifies itself as
 	  "2.2.[5678]-STABLE" after the 2.2.5-RELEASE.)
@@ -1918,7 +1918,7 @@ PKGMESSAGE       ${PKGDIR}/MESSAGE
 	  development on several branches made it infeasible to
 	  classify the releases simply by their real release dates.
 	  (Note that if you are making a port now, you don't have to
-	  worry about old -current's; they are listed here just for
+	  worry about old -CURRENT's; they are listed here just for
 	  your reference.)
 
       </itemize>