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

Re: [SURVEY] for repository administrators

From: <cmpilato_at_collab.net>
Date: 2003-04-16 01:34:36 CEST

Karl Fogel <kfogel@newton.ch.collab.net> writes:

> If you create Subversion repositories, please respond to this survey.
> Follow up to the whole list, not just to me personally. Keep the same
> subject line, though, so it's easy for people to filter out the
> responses.
>
> 1. Approximately how many repositories have you created since late
> January of this year?

Real persistent ones? Maybe 2 or 3. But hundreds in the course of
testing Subversion or ViewCVS, I'm sure.

> 2. Were you aware of the `--on-disk-template' option to
> 'svnadmin create'? If so, did you understand what it does?
> Do you use it [always|sometimes|never] when you create a
> new repository?

Aware -- yes. Understand -- yes. Use -- never.

> 3. Were you aware of the `--in-repos-template' option to
> 'svnadmin create'? If so, did you understand what it's for?
> Do you anticipate using it [always|sometimes|never]?

Aware -- yes. Understand -- yes. Anticipated use -- never.

I'm not fond, at all, of either of these template mechanisms, but
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. I don't care about making custom layouts automatically
available, but I *do* care about encouraging folks to use the one
layout which we are trying to promote as a sort of de facto standard.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 16 01:31:37 2003

This is an archived mail posted to the Subversion Dev mailing list.

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