John Rouillard wrote:
> If I want to see how many versions of an ldap config file has been
> released, I have to go to the log messages and look at all the
> revisions and count them (or use a program to do the same). Where
> revision 1.6 of the file tells me I have had 6 copies of the file with
> no requirement to be able to access the repository. If I know that the
> file is at revision 2010 in svn, does that tell me anything about the
> number of releases of this file? It does tell me about the repository,
> but if I only want a file number because it has no relation to the
> repository as a whole (e.g. a document rev number) then...
Just because you have (CVS style) revision 1.6 of a file, it doesn't mean
there have only been 6 changes to the file. What about the extra 10 changes
there might have been in a 1.2.1 branch?
If you promise not to branch, then file revision numbers do tell you a small
amount of information (which you can get in SVN from the log). But as soon as
you have branches, then a file revision number becomes much less meaningful.
> In my case I have to cherry pick files at different revisions into a
> single tag all the time because the files are loosely coupled but
> deployed as a single entity (system configuration) but I currently
> have 40 or so subsets of files that are totally independent. So I get
> revision 1026 of the ssh keys files, revision 223 of the ssh config
> files, revision 2230 of the ldap config files etc.
No wonder you are having trouble coping :-)
I'd be interested to know how this comes about - mainly so I can avoid
getting myself into the same situation!
--
Nikki Locke, Trumphurst Ltd. PC & Unix consultancy & programming
http://www.trumphurst.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 14 20:46:48 2006