svn: /pear/peardoc/trunk/en/chapters/rfcs/ header-comments.xml
[email protected] (Chuck Burgess)
| Newsgroups | php.pear.doc |
|---|---|
| Message-ID | <[email protected]> |
ashnazg Thu, 10 Sep 2009 14:43:11 +0000
Revision: http://svn.php.net/viewvc?view=revision&revision=288243
Log:
literal $Id$ and $Revision$ keywords used in sentences should not have been expanded by CVS
Changed paths:
U pear/peardoc/trunk/en/chapters/rfcs/header-comments.xml
Modified: pear/peardoc/trunk/en/chapters/rfcs/header-comments.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/rfcs/header-comments.xml 2009-09-10 14:19:03 UTC (rev 288242)
+++ pear/peardoc/trunk/en/chapters/rfcs/header-comments.xml 2009-09-10 14:43:11 UTC (rev 288243)
@@ -262,10 +262,10 @@
docblocks will use <literal>@package_version@</literal>, which gets
replaced with the release's version number by the PEAR installer.</para>
- <para>This seems the best compromise because <literal>$Id: header-comments.xml,v 1.4 2009-05-04 20:16:19 cweiske Exp $</literal>'s
+ <para>This seems the best compromise because <literal>$Id$</literal>'s
talk about files while the release version numbers talk about the
- classes. <literal>$Id: header-comments.xml,v 1.4 2009-05-04 20:16:19 cweiske Exp $</literal> is used rather than
- <literal>$Revision: 1.4 $</literal> or other shorter tags because it is the
+ classes. <literal>$Id$</literal> is used rather than
+ <literal>$Revision$</literal> or other shorter tags because it is the
standard and provides all of the potentially desired information.</para>
</section>