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

Repository management

From: Brass Tilde <brasstilde_at_insightbb.com>
Date: 2005-04-22 15:22:32 CEST

We are finally about to implement Subversion here at work, moving from PVCS,
and I'd like to get a feel for what folks think are some of the more useful
practices you've seen, and why you think they are useful. The two main
subject areas I'm interested in are layout and hook scripts.

WRT layout, have you found that having everything in one repository has
worked out for you, or have multiple repositories worked better. We have a
number of projects ongoing, which are related from a business standpoint,
but not so much from a software standpoint. However, they do share some
library code. The network manager doesn't seem to have a problem with
multiple repositories, just as long as it doesn't get ridiculous. :)

On the other subject, hook scripts, we've identified a few things that we
want to do, such as preventing commits with blank or non-existent log
messages, preventing commits where certain properties aren't set, such as
line-style, preventing commits when certain properties *are* set, such as
keyword expansion, preventing commits to tags, etc.

What types of things that can be done with hook scripts have you found to be
beneficial, or useless for that matter?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 22 15:24:39 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.