Jim Correia wrote:
> On Jun 17, 2005, at 12:52 PM, Rule, Chris wrote:
>
>> It seems to me the revision number absolutly does indicate a version of
>> a project at a given point in time.
>
>
> Of course it does - it represents exactly one version of the repository
> tree at a point in time.
>
It doesn't. Read what Ben wrote and what you wrote. They're not the same
thing. Be very careful here: one of these statements is true, and one is
false.
The revision indicates the version of a project.
The revision indicates the version of the repository.
Plus, there's 2 other problems here with using the revision number as a
"version" number. One is that tagging is going to increase your revision
number while making no changes to the source code. One project per
repository isn't going to change that.
Two is that a revision, be it per-project or per-repository, doesn't
give anyone any idea of what changed or by how much. You could commit a
change to a property, or you could do a total rewrite of the project and
commit it as one revision. Or two successive commits could make and then
reverse a change. The only useful information comes from the log. That's
why (I presume) Ben says that you're assigning meaning to the number
where there is none.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jun 18 00:16:54 2005