Subversion Revision Numbers driving me Batty. What about a SECOND revision number?

So here I am playing with subversion and looking at the repository I notice that
a file has the version 105. Now I know damn well that file has been changed
perhaps a grand total of 10 times but my version system tells me 105 times.

The issue I am grappling with is one of duality. While I understand the desire
and indeed need to upgrade the revision of the entire project at checkin time, I
find it annoying to have to see files that change seldom, if at all, to be so
highly numbered. Many CVS refugees will also likely find this weird.

As a senior developer, the low revision nubers tell me one of two things:

1) This piece of code is extremely stable.
or
2) This code coudl be extremely stale.

Now, Im not suggesting ditching the current revision numbering at all. However,
what would be the harm in introducing a new number. Since "Revision" is taken as
a concept, what about "File Version" ? This would simply store the number of
times one specific file had changed. In this matter I get all the benefit of the
current revision system without loosing any benefit of seeing file version.

So what impact would this happen? Unless you guys were all smoking pot when you
designed this thing (and heck if I know because my C is VERY rusty) it shouldnt
be a big modification to tack one extra number and one extra keyword,
$FileVersion: 5 $ into the system.

So what do you think?

-- Kraythe

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 22 00:11:03 2003