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

TortoiseSVN import similar to TortoiseCVS make new module?

From: Eric White <ewhite_at_ssc.wisc.edu>
Date: 2007-11-27 18:09:51 CET

Hello,

I've used CVS and the TortoiseCVS client for years and I'm just moving over
to subversion with TortoiseSVN. I wanted to run my thoughts by the list and
see if I'm understanding things correctly.

I've got two groups of developers who work on different sets of projects.
I'm thinking of arranging my repositories like this:

/developer_group_1
  /project_1
    /trunk
    /branch
  /project_2
    /trunk
    /branch
  /project_3
    /trunk
    /branch

/developer_group_2
  /project_A
    /trunk
    /branch
  /project_B
    /trunk
    /branch

So as long as I created the "developer_group_1" and "developer_group_2"
repositories, the developers in group 1 could use the import command on the
TortoiseSVN client to import files to "project_1", etc, while developers in
group 2 can do the same in their repository. I believe this would be
similar to our current method of developers creating a new module and then
committing in CVS.

I'm thinking of using 2 repositories because the developers in each group
should not have rights to access the files of the other group. Does this
seem sensible?

Right now the developers are running TortoiseSVN using ssh+svn, but we'll be
enabling webDAV, too.

Thanks a lot,

--
---------------------------------------------------------------
Eric White                           

  • application/x-pkcs7-signature attachment: smime.p7s
Received on Tue Nov 27 18:10:00 2007

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

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