Re: [SURVEY] for repository administrators

cmpilato@collab.net wrote:

>> ... since we as a community have established that we'd like to politically
>> push a recommended (/trunk, /tags, /branches) layout, I'd be +1 on a
>> single flag to svnadmin create, '--auto-layout', which created those
>> directories.

Sounds like a good idea. Maybe --auto-layout can have a
parameter (project-first vs. project-last) as well?

>>>>> "M" == Michael Price <michael.price@acm.org> writes:
M> Of course, you then have all of the people (like me) who think that
M> the top level directory should be project names with each project
M> having the appropriate subdirectories...

The initial template could contain:

    /skel/trunk /skel/tag /skel/branch /skel/README

and the tutorial could tell the user to run "svn copy $URL/skel
$URL/practice" before starting the practice area.

On the other hand, people who want to promote layout that has
trunk, tag, branch at the root level could use a template like
this:

    /trunk/skel/README /tag/skel /branch/skel

and tell the user to run 3 "svn copy" commands (to copy skel to
practice) in the tutorial.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 16 04:21:25 2003