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

Re: early reflections on subversion methodology

From: Thomas Beale <thomas_at_deepthought.com.au>
Date: 2005-07-29 11:28:42 CEST

Saulius Grazulis wrote:
> On Friday 29 July 2005 03:42, Steve Williams wrote:

> Actually, you can hide the directory of your project structure for developers
> without any modification of the client:
> Instead of checking out the whole repository:
> svn co svn://server.domain.org/repositories/project1 whole-project1
> You can just check out a trunk:
> svn co svn://server.domain.org/repositories/project1/trunk project1
> Or some branch:

Sure, and that is of course our advice in our help pages. But it doesn't
mean that people will understand that these directories are special; it
is not always easy to educate users who are not familiar with CM systems
  what trunk/tags/branches are about; some expect it to be built in,
others don't understand at all to begin with.

> svn co svn://server.domain.org/repositories/project1/RELEASE/version-11R6
> project1-view-11R6
> At your liking... :)
> You can also switch your working copy between any of the branches, tags or
> trunk.
> Enforcement of the directory structure is a matter of project administration.

At this stage of subversion's development, you are right; because there
is no other choice. But it would be nice if a facility were built into
the tool to e.g. make a trunk/tags/releases/branches directory "node" at
some point in your tree, and have svn manage that itself, and not sow
those as directories, but as a 'developmnet tree' or somesuch.

- thomas beale

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 29 11:48:49 2005

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.