On Tue, Nov 14, 2006 at 09:54:45AM -0500, Duncan Murdoch wrote:
> On 11/14/2006 9:21 AM, Les Mikesell wrote:
> >On Tue, 2006-11-14 at 01:38, Tim Hill wrote:
> >>Actually I think the single rev# is one of the best features of SVN.
> >>Having used "per-file" rev# systems, which deteriorate into chaos, I
> >>far prefer the Subversion approach. Plus the fact that, in effect, a
> >>rev# becomes a changelist.
> >It makes sense for a 'project'. It doesn't make much sense
> >for a collection of mostly unrelated files and it is cumbersome
> >to put each in its own repository.
> Why not? If you just think of revision numbers as tags,
Hence the problem. If you think of revision numbers as the count of
the number of revisions of the file not the repository. A file
activity counter if you will, then you loose information with the
repository version number. Both ways are right and wrong depending on
how the files relate to each other.
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.
(These revisions aren't always the same version I would get by
checking out the HEAD revision of the tree. I have sort of abandoned
this because of how difficult it is to track this where it was easy
under CVS with floating tags, but I digress.)
> they are just
> as meaningful whether they increase sequentially or by bigger jumps.
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...
603-643-9300 x 111
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Nov 14 18:42:31 2006