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

Re: versioning rant

From: Sean Russell <ser_at_germane-software.com>
Date: 2002-02-21 00:47:17 CET

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 20 February 2002 02:06 pm, Greg Stein wrote:
> > This is something cvs cannot do.
>
> It's something that we can't do either :-)

I /sort/ of understand, but sort of not.

CVS can /almost/ do this, with $Revision: $, except that there isn't one clear
version # for the whole project.

I understand the comment about bits from different revisions, I think (partial
updates? relocations?), but why wouldn't it be useful to do something
similar to $Revision: $ in the svn client/server executable? If someone does
an 'svn up' or 'svn co' and builds, which is probably the most common
behavior, wouldn't the version number be useful information to include?

- --
 |.. "Q: How can you delay milk turning sour?
<|> A: Keep it in the cow."
/|\
/|
 |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8dDWFP0KxygnleI8RAo9UAJ9fSZlZMdS4tAYmCukvR6ZvCQppHgCgsxQO
fluafM9I7W4mGqaVJz34rDI=
=EL0W
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:09 2006

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

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