[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: How to enable and use keyword substitution (a-la CVS)

From: David J. Marcus <djmarcus_at_m5inc.com>
Date: 2005-02-27 18:54:29 CET

Mark Phippard wrote:

>Read this:
>
>http://svnbook.red-bean.com/en/1.1/ch07s02.html#svn-ch-7-sect-2.3.4
>The gist of it is that you have to specifically tell Subversion what
>keywords you want to use by specifying those keywords in the svn:keywords
>property on the file.
>

I had actually read chapter prior to posting my questions.

>[...] Subclipse has a Team -> Set Keyword action that
>makes it easy to set these properties on the files. You will need to
>commit the prop changes before you see anything in the file.
>
>If you read further down in that same section of the document, it will
>describe auto-properties. This is a way to have the svn:keywords property
>set when files are initially added/imported.
>
>
I feel silly for not exploring the 'Team' submenus (I spent all the time
looking at Preferences).

There is still an issue of how the keyword substitution are made. Under
CVS each substitution generates new lines in the file that become part
of the updated file. The substitutions thus serve as a chronological
history that grows and is embedded right in the file. This is a very
useful feature. It seems that in Subversion you only see the last
substitution.

The value of just seeing the latest values of these substituted keywords
appears (at least to me) to have minimal vlaue. Just knowing who was
last to change the file (and on what date) is essentially useless. I
would still need to go into the revisions history to pick up the
descriptive comments of all the changes (and if required dig deeper into
the diff).. a lot of work to do for something that the Eclipse/CVS
plugi-in does well.

>Subversion does not support $Log$ and probably never will as the core
>developers seem opposed to it.
>
In all honesty, I'm very surprised. In our shop, all checked in code has
to have a 'description' (the gist of the change) which we programmers
find very useful when revisiting old code.

I suspect that the 'core' developers don't like the $Log$ because it is
not cumulatively substituted (as it is in CVS). Just seeing the last
description is not anywhere as useful as seeing all of them in
chronological order.

> I am sure they might consider a
>well-implemented patch. You can read the mailing list archives for past
>discussions on this.
>
>http://www.google.com/search?as_q=%24Log%24&as_sitesearch=svn.haxx.se
>
>
Thanks for the link, and for this very useful total repsonse to my inquiry.

-Regards
David

>Mark
>
>
>_____________________________________________________________________________
>Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
>_____________________________________________________________________________
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
>For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
>
>
Received on Mon Feb 28 04:54:29 2005

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.