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

repos-side config bits (was: svn:mime-type and detecting mergeability)

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-08-22 19:57:20 CEST

On Thu, Aug 22, 2002 at 12:23:26PM -0500, cmpilato@collab.net wrote:
> > Karl Fogel <kfogel@newton.ch.collab.net> writes:
> > > Eric Gillespie <epg@pretzelnet.org> writes:
> > > > He thinks this should be a repository option (which places it
> > > That sounds good to me. And we can implement the client side now,
> > > leaving the repository side for post-1.0.

Adding features, Karl? Alpha means they go into the post-1.0 bucket and need
to "work hard" to get out of the bucket. IMO, this feature doesn't really
seem to hit the bar for a post-alpha feature addition.

[ of course, if a patch comes along and it is obviously low-impact... ]

> I dunno, Ben. I think it would be cool if Subversion's repository
> could propogate default config options to working copies associated
> with that repository. Think repos-wide svn:ignores,
> svn:textual-mimetype, etc.

And a replacement for CVS's rcstemplate (the default text for commits that
pop up $EDITOR).

> Without such, every user, on every machine
> on which they use Subversion, has just that many more magic steps they
> have to take before their working copies are properly set up. What's
> more, those configuration may not be desirable for all working copies
> they have -- these are per-repository types of options.


It would be nice to file these as post-1.0, tho...


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 22 19:53:04 2002

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.