[PATCH] Repo layout

Blair Zajac blair at orcaware.com
Mon Dec 19 11:51:41 CST 2005

Martin A. Brooks wrote:
> Hi
> A user on the IRC channel felt it would be helpful if the book pointed 
> out a particular downside of the "all in one" repo layout option.  The 
> attached patch does just that.
> Regards
> Martin A. Brooks
> ------------------------------------------------------------------------
> Index: ch04.xml
> ===================================================================
> --- ch04.xml	(revision 1906)
> +++ ch04.xml	(working copy)
> @@ -1995,6 +1995,15 @@
>          longer exists, and the user will be forced to <command>svn
>          switch</command> to the new location.
>          </para>
> +	
> +     <para>One problem with mixing multiple projects within one
> +       repository is that users may become confused about which
> +       commits apply to <emphasis>their</emphasis> project.  This is
> +       especially true if, as is commonly the case, a commit to the
> +       repository triggers an automated email message to the
> +       development group. A user working on a less busy project may
> +       have to sift through dozens of emails that have nothing to do
> +       with their work.</para>
>      </sect2>

The standard method of dealing with this is using the mailer.py and a 
mailer.conf that sends email to the people that care about particular portions 
of the repository, so people don't have th slog through emails they don't care 

Regarding repository administration, it's much easier to have a single 
repository that contains all the projects and manage the mailer.conf file than 
it is to have one repository for each project, as you'll still need to manage 
the mailer.conf's to get the correct email addresses for each repository.

I would suggest that the patch be modified to review this description.


Blair Zajac, Ph.D.
<blair at orcaware.com>
Subversion and Orca training and consulting

More information about the svnbook-dev mailing list