[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Best practices rookie question.

From: claudia logan <cvlogan1_at_yahoo.com>
Date: Fri, 25 Jan 2008 15:54:50 -0800 (PST)

Hi all,
    Rookie question regarding branching/tagging and baselining. We have a public library where the release will be used on several projects. The Public library folder has its' own life and release - i.e. trunk,branches,tags. (see layout below)

Question 1: Using TortoiseSVN, How do I create a branch where only 3 of the 5 directories are branched. what are the best practices. What I have done is branched the complete trunk then remove what I dont need. But that seems counterproductive. I updated the repository twice when there was no need.

Question 1b: related to above, but instead of folders, individual files. I may need 5 documents out of 10. All located in the same area. How do I tag only what I need, leaving the rest?

Question 2: Since I need "Public library-v1.0" as part of Project B, what is the best way to package it as one tool? The goal being that by extracting the project-tag, it will contain all that I need to release. What I've done, is export the version "Public library-v1.0" into my "Project B - tag". and then update my tag...But it does not seem right. What is the best way....

Here is the layout of my repository, using TortiseSVN (http):



                        /Tags/ v1.0

Any and all help is appreciated...


Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Received on 2008-01-26 00:55:20 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.