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

[Request] TSVN Server ;-)

From: Peter Mounce <pmounce_at_narrowstep.com>
Date: Mon, 28 Apr 2008 13:29:11 +0000 (UTC)

Hi there

There are a bunch of settings that it would be really nice to apply consistently
to the users of the repositories that I manage. I'm thinking here mostly
about the client-side hook-scripts, but there are others like global-ignore
pattern, proxy server and maybe some others.

I guess at the moment this would be possible to do by setting up one workstation,
then exporting the registry entries that are created? And making the assets
(client-side hook-scripts) available either via a network share, or a WC
checked out locally?

It'd be nice if there were a facility to supply settings from some central
location, whether these are global settings, or per-repository settings (I
could see client-side hook-scripts varying per-repo, for example). I suppose
this might be along the lines of an XML file sat on a server that, when pinged,
populates settings according to the contents of the file...? Perhaps a per-repo/project
set of settings could be grabbed from a file in a consistent/conventional
location within a repo? Perhaps a set of tsvn:* properties would do the
job, to define settings to apply to the directory tree they're set on?

Perhaps this is better asked for on the svn-users list, but, well, maybe
it's a function of the interface instead, since I think the settings I'd
like to manage are only relevant to TSVN (client-side hook-scripts, again).

I'm in the position of being "tools-guy" for a team of around 9, and, well,
it'd help to have (easy :-) ) capability for this sort of thing.

Best regards
Pete

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-04-28 15:40:49 CEST

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

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