[Zope-Checkins] Re: [Zope3-checkins] SVN: Zope3/trunk/ Ignore files/directories that are result of a build process, such

Jim Fulton jim at zope.com
Thu May 13 07:12:59 EDT 2004


Stephan Richter wrote:
> On Thursday 13 May 2004 01:48, Fred Drake wrote:
> 
>>On Thursday 13 May 2004 01:21 am, Philipp von Weitershausen wrote:
>> > Yup. Btw, the "$Id$" keyword issue has not been fixed yet. We need to
>> > set svn:keywords="Id" on every file where we want the Id keyword to be
>> > expanded. To make svn pick it up, the original string needs to read
>> > "$Id$". A previous CVS expansion of the Id keyword will not get picked
>> > up by svn.
>>
>>Perhaps we should examine "the issue" a little more carefully.  Do we
>>*want* $Id$ expansions, or anything else expanded?  I've never seen it as
>>anything but docstring pollution, but I know Jim likes it.

In theory, $Id$ expansion is useful for determining the version of *deployed*
software.  In practice, well, I'm not sure we ue it in practice. I'm not aware
that we do. While I've thought for a long time that it would be useful and, in
early versions of Principia, has a specual method for getting a sites id strings,
I've never used this facility in all the years Zope (and Principia) have been
around.

IOW: WHUI (We haven't used it)

For development, it just gets in the way.  In CVS. I recommend that people use
-kk, which disables substitution, to prevent spurious merge conflicts.
Subversion doesn't seem to have such an option, so enabling $Id$ could cause
major headaches for merging.

> I like them too. :-) They give me a quick overview who and when the file was 
> last modified.

Sure, but I doubt that this benefit is really worth the cost.

I'm for saying good bye to $Id$.

Jim

-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org




More information about the Zope-Checkins mailing list