Brad Appleton wrote:
> However, I would still want a way to associate a name with a
> revision-number that was simply an alias for the revision-number
> and didn't create a new copy in the pathspace because I don't
> want that level of visibility for every commit - just the
> ability to use a pseudonym for global revision number. The
> example I gave of a 'NAME=' revision keyword would do this,
> and (unlike a property I assume?) be able to be used in
> revision ranges given to svn log and svn diff.
Remember that the Subversion pathspace is hierarchical - and nobody in
their sane minds will checkout all of it.
So, for example, you could create "revnames" directory somewhere, and
stash them all there. The revision names there could be used without
anyone ever taking a directory listing of that - and it would even
enforce uniqueness, since overwriting a directory is not allowed (by
the Subversion client). Or, if you wish to have decent listings of
tags as well, you can organize them hierarchically by project and by
purpose. Or whatever.
If you think that creating a new copy in the pathspace gives too much
visibility, it is time to organize the pathspace so that it does
not. Subversion is giving you all the tools to decide your own
conventions, but it is up to you to find the conventions that work for
you.
Hell, you could write a book on Subversion repository pathspace
patterns ;-)
-- Naked
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 29 12:36:50 2004