+2  A: 

subversion handles the revision number per project not per file as cvs used to

Nikolaus Gradwohl
+4  A: 

Revision numbers do not count how often a particular controlled artifact has been modified. Rather, they track a version of the entire set of artifacts. This way you can retrieve, say, version 96 and know based on that number that you have exactly the set of files that you need.

This is different from CVS or VSS where version numbers are tracked on a per-file basis and you need a different technique to get a consistent entire-project view. (E.g., "labels" in VSS)

Greg D
THanks for you help I think I figured out a soln
dewalla
I was just thinking, how does this answer the question...
Kwebble
It answers the question because it explains how the numbers "skip". It looks like versions on a file are skipped because the file hasn't changed for one or more checkins.
Greg D
+2  A: 

As others have said, you can't do that in Subversion. And you don't need to. If you want to know how many revisions have been made to a particular file, use svn log.

Zac Thompson