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

Re: per-project version numbers - a way to support them? (without changing Subversion!?)

From: Scott Palmer <scott.palmer_at_2connected.org>
Date: 2005-09-16 19:37:09 CEST

On 16-Sep-05, at 11:48 AM, Johnson, Rick wrote:

> If that's truly the case then people like yourselves need to explain
> themselves better. You said in a previous message: "It's not like the
> numbers have any significant meaning". That's a pretty strong
> statement
> of non-meaning since significant is a fuzzy word in English. The
> revision number is purely a way of saying "state of repository and a
> certain point in time". That is always significant to me.
> Rick

Yes I could have been more clear. I meant significant to the project
vs. significant to the repository. I don't think the revision number
of the repository is of much significance with respect to the
project. I.e. it can change by thousands and it doesn't mean that
the project has a thousand additions or bug fixes or features added.
It could just mean that someone went through and applied something
like svn:eol-style=native using an inefficient script. It is of
course significant with respect to the repository. The idea that
someone might treat it as a project version number, when it simply
isn't anything like that, is where people run into trouble.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 16 19:37:28 2005

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.