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

RE: $Rev$ and viewcvs

From: Roger Talkov <rctalkov_at_appworx.com>
Date: 2004-04-19 15:23:34 CEST

Try wenSVN
http://websvn.tigris.org/

Roger Talkov
 
AppWorx
425-644-2121 x135

-----Original Message-----
From: cmpilato@localhost.localdomain [mailto:cmpilato@localhost.localdomain]
On Behalf Of C. Michael Pilato
Sent: Monday, April 19, 2004 6:05 AM
To: Luis Caņas
Cc: subversion mailing list
Subject: Re: $Rev$ and viewcvs

Luis Caņas <lcanas@gsyc.escet.urjc.es> writes:

> But these tags are not interpreted when we use the web interface
(viewcvs).
> It's very important for me to keep the revision number of a file text,
> but I don't know to do that ....

Subversion != ViewCVS. This message belongs on the viewcvs@lyra.org
list.

But I'll spare you the trouble -- ViewCVS is a repository browser, and
performs no transformations on the data stored in that repository.
Since Subversion stores keywords unexpanded in the repos (and expands
them client-side), this is the behavior you'll see using the ViewCVS
'svn' module. That said, if you can deal with slower and unfinished
behavior, you can setup your ViewCVS configuration to point to not the
path of your repository, but it's URL (even a file:/// URL will do).
That will cause ViewCVS to start using the not-highly-publicized
'svn_ra' module, which is a client-side wrapper -- that *should* show
your files with the $Rev$ and such expanded.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 19 15:22:52 2004

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

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