Re: [PEAR-DEV] Re: [PEAR-DOC] Re: [PEAR-DEV] PEAR CS Documentation Incorrect?

[email protected] (Jan Rosier)
Newsgroups php.pear.dev,php.pear.doc
Message-ID <[email protected]>
With subversion keyword substitution is "file-based". You can turn it  
off by removing the svn:keywords property on that file.

With no svn:keywords property set on that file, Subversion will do  
nothing special.

http://svnbook.red-bean.com/en/1.5/svn-book.html#svn.advanced.props.special.keywords

Just my 2 cents,
Jan Rosier

On Sep 9, 2009, at 1:31 PM, Ken Guest wrote:

> Chuck
> you're proposed solution makes sense - it is an example after-all...
>
>
> k.
>
> On Wed, Sep 9, 2009 at 12:24 PM, Chuck Burgess  
> <[email protected]> wrote:
>
>> On Mon, Sep 7, 2009 at 2:38 PM, Mark Wiesemann <[email protected]>  
>> wrote:
>>
>>> Hannes Magnusson wrote:
>>>
>>>> As you can see by the highlighting, that example is b0rked.
>>>> I assume the documentor was trying to prevent the $Id$ keyword  
>>>> being
>>>> expanded by SVN.
>>>> This _could_ also be a bug in the application rendering the markup
>>>> (PhD)...
>>>>
>>>> Please file this as a documentation bug report :]
>>>>
>>>
>>> The bug report already exists since March:
>>> http://bugs.php.net/bug.php?id=47679
>>>
>>> Regards,
>>> Mark
>>
>>
>>
>> I took a look at that PHP bug, as well as looking at both the  
>> example in
>> the
>> docs and its source in standards.xml.  Since both occurrences are  
>> examples
>> of usage, should it matter if CVS/SVN expands the $Id$ keyword?  If  
>> it
>> doesn't, then the example shows you what you should write in your  
>> @version
>> tag... if it does, the example shows what a fully expanded @version  
>> tag
>> looks like.  Either/both are reasonable example content, IMO.  If  
>> there are
>> no objections to this line of thinking, then I can solve the bug by  
>> simply
>> using "$Id$" in those two instances and commit it.
>>
>> Thoughts?
>> --
>> CRB
>>
>
>
>
> -- 
> http://blogs.linux.ie/kenguest/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.