Re: One Repository or Multiple?

Ben Gollmer wrote:
>
> > The benefits of multiple repositories, that I can think of:
> >
> > * Version numbers stay lower. (But if you're worried about this
> > you're probably doing something wrong.)
> >
> > * Can be moved independently if components want to be re-hosted
> > elsewhere.
> >
> > * Can be backed up independently, which may lead to less backup media
> > usage or more easily compartmentalized backups.
> >
>
> If you set up per-project mailing lists like I did, it's easy to use the
> provided post-commit scripts to send mail on each commit if you have seperate
> repos's for each project.
>
> If you've got multiple projects within one repository and want each one to
> have it's own mailing list, be prepared for some script hacking.

Not true. The supplied commit-email.pl script takes an optional regular
expression command line argument which specifies which commits go to
which email addresses.

For example, in my repos, I have this in the post commit script:

# Send an email out showing the differences in this commit.
"$REPOS/hooks/commit-email.pl" "$REPOS" "$REV" \
  -m '^(branches|tags|trunk)/orca' orca-checkins@orcaware.com \
  -m '.*' blair@orcaware.com &

See the commit-email.pl usage info for more info.

Best,
Blair

-- 
Blair Zajac <blair@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org