> 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.
Not exactly. What you describe is how the $Log$ keyword behaves. The
issue is just that svn does not support that keyword. The rest of the
keywords, the one svn does support, behave similar to their CVS
counterparts.
As for the rest of your points, if you read some of the mailing list
threads I sent you, you will find answers to all of your questions. The
devs have their reasons why they are not supporting this keyword. Some of
them, such as Karl Fogel, originally worked on CVS so perhaps they just had
problems supporting that keyword and did not want to bring the burden into
Subversion.
As others have pointed out the svn log command serves as a decent
replacement.
By the way, even though there is a specifc UI for setting keywords, they
are just svn properties. So you can also just use the standard UI for
maintaining properties, and just use it to maintain the svn:keywords
property.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Mon Feb 28 06:47:00 2005