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

Re: working-revision keyword

From: Lixuesong <givemenews_at_tom.com>
Date: Wed, 3 Sep 2008 17:13:27 +0800

the way descripted in FAQ "Why doesn't the $Revision$ keyword do what I want? It expands to the file's last-changed revision, but I want something that will expand to the file's current revision."
is not ideal since it depends on svn command 'svnversion'.
if I compile source code in a machine which no svn installed, the compile will fail since it doesn't know what is svnversion.

----- Original Message -----
From: "Roth, Pierre" <pierre.roth_at_covidien.com>
To: "Lixuesong" <givemenews_at_tom.com>
Cc: <users_at_subversion.tigris.org>
Sent: Wednesday, September 03, 2008 4:50 PM
Subject: RE: working-revision keyword

> -----Message d'origine-----
> De : Lixuesong [mailto:givemenews_at_tom.com]
> Envoyé : mercredi 3 septembre 2008 10:36
> À : Roth, Pierre
> Objet : Re: working-revision keyword
>
> I've got an answer for FAQ "Why doesn't the $Revision$
> keyword do what I want? It expands to the file's last-changed
> revision, but I want something that will expand to the file's
> current revision."

Please answer to the list too.

The current version of the file is the same as the last-changed, isn't it ?
You local changes do not have a revision yet: they will have one when committed to the repository.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-03 11:14:08 CEST

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