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

RE: Global Revision keyword, again and again

From: Christopher Ness <chris_at_nesser.org>
Date: 2005-07-30 04:40:15 CEST

On Sat, 2005-07-30 at 01:18 +0200, Jan W. Hentsch wrote:
> This is really different, so the feature I'd like to see would only make
> sense after an update, that did I understand now.
> But it would still be very usefull for me and possibly others as well.
>
> Maybe there could be an extra option to the update subcommand. which
> triggers the update of the "YoungestChild" keyword in the fixed file.

I don't understand.

You suggested a file with the revision number in it. This could be
created with the command `svnversion .` for the working copy.

As you should be aware by now, knowing the global revision number at the
time of a build does not have any meaning. The revision range (x:y) of
the file set that you compile is what is important to your program and
tracking down bugs. This is what `svnversion` gives you, the range of
revisions.

Here is a link to the FAQ for those who haven't read it yet.
  http://subversion.tigris.org/faq.html#version-value-in-source

Cheers,
Chris

-- 
PGP Public Key: http://www.nesser.org/pgp-key/
22:27:48 up 3:24, 3 users, load average: 0.10, 0.06, 0.01

Received on Sat Jul 30 04:40:37 2005

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