Best practices rookie question.

[claudia logan <cv...@yahoo.com>]

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):

Project_A/Trunk/Folder_1
                              /Folder_2
               /branch
            /tag

Project_B/Trunk/Folder_1
                              /Folder_2
                              /Folder_3
                              /Folder_4
              /branch
             /tag
 
 Project_n/.....

 Public_Files/Trunk
                       /Branches
                        /Tags/ v1.0
                                    /v#...

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 

RE: Re: Best practices rookie question.

[Paul Koning <pk...@equallogic.com>]

Given that branches are "free", my practice is simply to branch right
near the root of the repository.  Much of the branch isn't needed, but
it doesn't cost anything.  The part that isn't needed won't change, so
it takes no extra space to speak of.

Don't bother deleting what you don't need, you're (1) wasting time, and
(2) wasting space -- because it takes more space to record the deletion
than to leave things alone.

This is one place where you really need to unlearn your CVS lessons --
CVS branching is very very bad while Subversion does this right and very
efficiently.

	paul

> -----Original Message-----
> From: marc gonzalez-carnicer [mailto:carnicer.lists@gmail.com] 
> Sent: Friday, January 25, 2008 9:24 PM
> To: claudia logan
> Cc: users@subversion.tigris.org
> Subject: Re: Best practices rookie question.
> 
> 
> hi,
> 
> 2008/1/26, claudia logan <cv...@yahoo.com>:
> > 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.
> 
> i would not remove after branching. if you merge back to trunk, the
> removed items will be removed.
> 
> >
> > 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?
> 
> it seems you haven't remarked yet that copying (branching) is 
> 'cheap', i.e., it
> does not take up disk space. otherwise, i don't see why you 
> would want to
> tag some subset of the files.
> 
> if you really need to release a subset of documents, what i'd do is :
> 
>  * create a release/export folder on the repo
>  * svn copy there the needed files
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Best practices rookie question.

[marc gonzalez-carnicer <ca...@gmail.com>]

hi,

2008/1/26, claudia logan <cv...@yahoo.com>:
> 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.

i would not remove after branching. if you merge back to trunk, the
removed items will be removed.

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

it seems you haven't remarked yet that copying (branching) is 'cheap', i.e., it
does not take up disk space. otherwise, i don't see why you would want to
tag some subset of the files.

if you really need to release a subset of documents, what i'd do is :

 * create a release/export folder on the repo
 * svn copy there the needed files

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org