<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.5730.11" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=588353221-15012007><FONT face=Arial
color=#0000ff size=2>The revisions are repository-wide.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=588353221-15012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=588353221-15012007><FONT face=Arial
color=#0000ff size=2>I believe that the ACLs could be configured based on
directory:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=588353221-15012007><FONT face=Arial
color=#0000ff size=2><A
href="http://svnbook.red-bean.com/en/1.2/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz.perdir">http://svnbook.red-bean.com/en/1.2/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz.perdir</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=588353221-15012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=588353221-15012007><FONT face=Arial
color=#0000ff size=2>and mailing list functionality could probaby be placed into
a post-commit hook script that parses the paths of the committed files and sends
the note to the appropriate -commit list.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=588353221-15012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=588353221-15012007><FONT face=Arial
color=#0000ff size=2>Jason</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <B>On Behalf Of </B>Robert
Bray<BR><B>Sent:</B> Monday, January 15, 2007 13:23<BR><B>To:</B> FDO Internals
Mail List; Shawn Barnes<BR><B>Subject:</B> Re: [fdo-internals] More Site
Cleanup<BR></FONT><BR></DIV>
<DIV></DIV>SVN can only provide access control, revisions, mailing list, etc at
the repository level. So to merge them into one repository would mean the
commiter list would need to be the same for all of FDO. I don't really have an
issue with that approach, but that is not the way it is setup
currently.<BR><BR>Bob<BR><BR>Jason Birch wrote:
<BLOCKQUOTE cite=mid8E468917B01800408B91984428BE03DD05853033@starfish.nanaimo.ca
type="cite">
<META content="MSHTML 6.00.5730.11" name=GENERATOR>
<DIV dir=ltr align=left><SPAN class=854135220-15012007><FONT face=Arial
color=#0000ff size=2>Is there a reason why you are staying with multiple SVN
instances, instead of merging the providers into the core and
managing access at the node level?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=854135220-15012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=854135220-15012007><FONT face=Arial
color=#0000ff size=2>I'm pretty sure that Trac instances have to have a 1:1
relationship with SVN repositories.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=854135220-15012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=854135220-15012007><FONT face=Arial
color=#0000ff size=2>Jason</FONT></SPAN></DIV><BR></BLOCKQUOTE></BODY></HTML>