Re: general source control strategy for many projects and many developers

On Jan 3, 2008, at 09:20, Ryan Jarvis wrote:

> On the server, I would like to have a bunch of source dirs like
> "calc", "calendar", "spreadsheet" etc. with the trunk, tags and
> branches subfolders underneath.

You mean: in the repository. These would not be directories on the
server's hard disk.

> I would like my end-users to create a project dir called "projects"
> on their local development machines and inside it only checkout the
> source dirs that are currently relevant to them. For example,
> "calc" and "spreadsheet".
>
> Now, the process for my end-users I want to be the same: using
> TortoiseSVN or equivalent, they run the commands 'update' and
> 'commit' on the "projects" dir only, not on any source dir
> underneath it.

Note that performance will be better if the user issues the "commit"
or "update" command only on the subdirectory they're actually working
on. If the user knows she has not modified any files in any other
directories, it is inefficient to still make Subversion look for
changes in those directories.

> During the update, I want their projects dir to only pull down the
> changes to the source dirs they have currently checked out. During
> the commit, I want all changes in all their source dirs to be
> checked in as a single revision.
>
> Is this situation possible out of the box? [snip]

I believe the non-recursive checkout feature might meet your needs:

svn co -N url://to/projects
cd projects
svn up calc
svn up spreadsheet

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-04 08:25:09 CET