cvs: peardoc /en/chapters standards.xml

From: Date: Wed, 12 May 2004 22:21:47 +0000
Subject: cvs: peardoc /en/chapters standards.xml
Groups: php.pear.doc 
Request: Send a blank email to pear-doc+get-3963@lists.php.net to get a copy of this message
danielc Wed May 12 18:21:47 2004 EDT Modified files: /peardoc/en/chapters standards.xml Log: Tabs to spaces. http://cvs.php.net/diff.php/peardoc/en/chapters/standards.xml?r1=1.15&r2=1.16&ty=u Index: peardoc/en/chapters/standards.xml diff -u peardoc/en/chapters/standards.xml:1.15 peardoc/en/chapters/standards.xml:1.16 --- peardoc/en/chapters/standards.xml:1.15 Wed May 12 18:13:12 2004 +++ peardoc/en/chapters/standards.xml Wed May 12 18:21:45 2004 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1" ?> -<!-- $Revision: 1.15 $ --> +<!-- $Revision: 1.16 $ --> <chapter id="standards"> <title>Coding Standards</title> @@ -22,10 +22,10 @@ (setq tab-width 4 c-basic-offset 4 c-hanging-comment-ender-p nil - indent-tabs-mode - (not - (and (string-match "/\\(PEAR\\|pear\\)/" (buffer-file-name)) - (string-match "\.php$" (buffer-file-name)))))) + indent-tabs-mode + (not + (and (string-match "/\\(PEAR\\|pear\\)/" (buffer-file-name)) + (string-match "\.php$" (buffer-file-name)))))) </programlisting> </para> <para>Here are vim rules for the same thing: @@ -285,9 +285,9 @@ <term>RELEASE_<replaceable>n_n_n</replaceable></term> <listitem> <simpara> - (required) Used for tagging a release. If you don't use it, - there's no way to go back and retrieve your package from the - CVS server in the state it was in at the time of the release. + (required) Used for tagging a release. If you don't use it, + there's no way to go back and retrieve your package from the + CVS server in the state it was in at the time of the release. </simpara> </listitem> </varlistentry> @@ -295,11 +295,11 @@ <term>QA_<replaceable>n_n_n</replaceable></term> <listitem> <simpara> - (branch, optional) If you feel you need to roll out a - release candidate before releasing, it's a good idea to make a - branch for it so you can isolate the release and apply only - those critical fixes before the actual release. Meanwhile, - normal development may continue on the main trunk. + (branch, optional) If you feel you need to roll out a + release candidate before releasing, it's a good idea to make a + branch for it so you can isolate the release and apply only + those critical fixes before the actual release. Meanwhile, + normal development may continue on the main trunk. </simpara> </listitem> </varlistentry> @@ -307,11 +307,11 @@ <term>MAINT_<replaceable>n_n_n</replaceable></term> <listitem> <simpara> - (branch, optional) If you need to make - <quote>micro-releases</quote> (for - example 1.2.1 and so on after 1.2.0), you can use a branch for - that too, if your main trunk is very active and you want only - minor changes between your micro-releases. + (branch, optional) If you need to make + <quote>micro-releases</quote> (for + example 1.2.1 and so on after 1.2.0), you can use a branch for + that too, if your main trunk is very active and you want only + minor changes between your micro-releases. </simpara> </listitem> </varlistentry> @@ -376,11 +376,11 @@ <informaltable> <tgroup cols="3"> <tbody> - <row> - <entry><simpara>Log</simpara></entry> - <entry><simpara>Net_Finger</simpara></entry> - <entry><simpara>HTML_Upload_Error</simpara></entry> - </row> + <row> + <entry><simpara>Log</simpara></entry> + <entry><simpara>Net_Finger</simpara></entry> + <entry><simpara>HTML_Upload_Error</simpara></entry> + </row> </tbody> </tgroup> </informaltable> @@ -399,12 +399,12 @@ <informaltable> <tgroup cols="4"> <tbody> - <row> - <entry><simpara>connect()</simpara></entry> - <entry><simpara>getData()</simpara></entry> - <entry><simpara>buildSomeWidget()</simpara></entry> - <entry><simpara>XML_RPC_serializeData()</simpara></entry> - </row> + <row> + <entry><simpara>connect()</simpara></entry> + <entry><simpara>getData()</simpara></entry> + <entry><simpara>buildSomeWidget()</simpara></entry> + <entry><simpara>XML_RPC_serializeData()</simpara></entry> + </row> </tbody> </tgroup> </informaltable> @@ -417,11 +417,11 @@ <informaltable> <tgroup cols="3"> <tbody> - <row> - <entry><simpara>_sort()</simpara></entry> - <entry><simpara>_initTree()</simpara></entry> - <entry><simpara>$this->_status</simpara></entry> - </row> + <row> + <entry><simpara>_sort()</simpara></entry> + <entry><simpara>_initTree()</simpara></entry> + <entry><simpara>$this->_status</simpara></entry> + </row> </tbody> </tgroup> </informaltable> @@ -500,7 +500,7 @@ // | Your Name <you@example.com> | // +----------------------------------------------------------------------+ // -// $Id: standards.xml,v 1.15 2004/05/12 22:13:12 danielc Exp $ +// $Id: standards.xml,v 1.16 2004/05/12 22:21:45 danielc Exp $ require_once 'PEAR.php'; @@ -552,7 +552,7 @@ * @category categoryname * @package packagename * @author Original Author <author@example.com> - * @version $Id: standards.xml,v 1.15 2004/05/12 22:13:12 danielc Exp $ + * @version $Id: standards.xml,v 1.16 2004/05/12 22:21:45 danielc Exp $ * @access public * @see NetOther, Net_Sample::Net_Sample() * @since Class available since Release 1.2.0

« previous php.pear.doc (#3963) next »