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

Re: SVN Revision of a whole working dir as a keyword ?

From: fj <fj_at_effjay.com>
Date: 2007-09-19 07:37:03 CEST

Ryan Schmidt wrote:
> On Sep 18, 2007, at 18:01, fj wrote:
>> Leonel Gayard wrote:
>>> I have a README file at the root of my project. In this README file, I
>>> have written: "This is project Blah, revision $Rev$".
>>> SVN correctly substitutes the $Rev$ keyword with the revision number
>>> of file README. The problem is, sometimes other files in the project
>>> are commited, which increases the overall revision, but not the
>>> revision of file README. So, when my users see that file, they see a
>>> different revision number than the revision number of their working
>>> copies.
>>> How can I have my file show the revision number of the working copy ?
>>> Yes, I've already RTFM.
>> I believe your only option is to segregate what to you is a distinct
>> "project" into its own repository, because the revision numbers in
>> svn are repository-wide. Or, I suppose, you change your process and
>> how you make use of the revision numbers you get.
> fj, that's not the issue at all. The problem is that Leonel wants the
> README to contain the latest revision of any file of the project, but
> the $Rev$ keyword only expands to the latest revision of the README file.
> Leonel, you'll probably need to do it as in this FAQ item:
> http://subversion.tigris.org/faq.html#version-value-in-source
> You'll have a file like README.in from which, in conjunction with the
> svnversion command, you can generate the final README that you
> distribute.
ryan - you're correct. I mis-read Leonel's description.
thank you.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 19 07:37:21 2007

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.