Re: Subversion vs CVS for document files

On Tue, 2006-11-14 at 12:21 -0500, John Rouillard wrote:

> 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.

I think what you really want is to maintain the systems as branches
in the first place, but I haven't come up with a way to import
things in a way that gives them a common parent and maintains the
common base versions on a trunk with only the differences in the
branches. Has anyone worked out a scheme for this where the
(slightly) differing versions already exist as a starting point,
then ongoing changes are made in one of the branches and may or
may not be propagated to the trunk and other branches? I'd love
to be able to 'svn diff' all or any configs from one machine to
another as well as different timeframes.

-- 
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org