Re: Change the existing schema in minting repository structure.

Hi,

On 10 February 2010 13:53, raghava.P <raghav.pattaswami_at_itpeoplecorp.com> wrote:
> Hi,
>        Greetings to all,
>
>                  I am using “tortoisesvn “, presently we are using separate
> repository for each project like Proj-A, Proj-B, Proj-C (in each Project we
> have Different folders like Dev, Testing, Production).  But I would like to
> move all these Projects under one roof i.e. in Projects/Proj-A,
> Projects/Proj-B, Project/Proj-C.
>
>  Here I have some doubts
>
> 1.      Easy method to move repository, Proj-A to Project/Proj-A without losing
> any revision history.
>

Using svn-move or svn-copy will preserve history (just uncheck the
'stop on copy' option when viewing the log).

> 2.       If I change in one of the folders in Proj-A then commit will change the
> revision history of the root
>         folders Project. To overcome this problem suggest any method.
>

You just accept this. Revision numbers are repository wide, so all
projects in the same repository share the revision numbers.

> 3.        Advice to me which is the best method, stick to existing one or Move to
> new schema.
>

Either method has its benefits. Neither is the 'best' one. If there is
any possibility of sharing code between the projects, using a single
repository has benefits (although it can be solved with 'externals'
from another repository too).

-- 
Regards,
Jean-Marc
--
.       ___
.  @@  // \\      "De Chelonian Mobile"
. (_,\/ \_/ \     TortoiseSVN
.   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
.   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2446410
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].