Saulius Grazulis wrote:
>On Friday 24 February 2006 19:43, Vincent Starre wrote:
>
>
>
>>The confusion of your actual intent comes from my having no idea why
>>you'd want to tag something (a revision number) which is, by itself
>>(without an associated path), meaningless.
>>
>>
>
>Indeed, this is the source of confusion. I can not grasp why you claim that
>revision number is meaningless? Given that revision number is the *only* way
>to access previous history of the project...
>
>
This thread seems to have run its course and died off further-down, but
I'd just like to clarify that a revision number is only 100% meaningless
by itself- that is (as said before) /without/ an associated path.
The only way to access a previous point in the project's history is by
knowing that point's revision number (or an associated translation, such
as a date for "state on or before") _AND_ knowing the path to that project.
If your repository is set up in such a way that absolutely every file on
it is absolutely essential to understanding absolutely every other file
on it, maybe a repository-wide revision number /without/ an associated
path would be fine for you (you could just assume the associated path is
"the root of the repository" in all cases- still an associated path)
And as said previously in this thread, there's still nothing stopping
you from tagging your repository root if that's your particular case.
Summary: Revision numbers _are_ important. They have much meaning when
in context. Without context they serve no purpose at all. (even "show me
the log up to revision 12598" is meaningless until you read the log.
"Show me the log at /tags/release-13" has paths cheaply associated with it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Feb 26 20:46:46 2006