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

RE: hooks in sub repositories

From: Robert Hunter <robert.hunter_at_gen-i.co.nz>
Date: 2005-03-22 23:27:54 CET

Marino Kevin wrote:
> We a repository located inside another repository and and when using hooks
> we have to put the files in the root repository hooks directory. Is this
> correct and how do we utilitize the sub repository hooks directory.
> Here is the layout of the repositories
> Root Repos.
> |
> |-- myRepos
> |
> |-- otherRepos
> so I can't seem to fire hooks in the myRepos or otherRepos directories.

What do you mean by a repository inside another repository?

As far as I know, a Subversion repository must reside on a real
OS filesystem. Although a repository contains trees of files
and folders, this "virtual" filesystem is not somewhere you
could create a second repository.

Perhaps mean two folders off the root of the virtual filesystem
provided by a repository?

Subversion only calls one hook script (of each type) for a
repository, but it is entirely possible to use hook scripts
that behave differently depending on the folder(s) affected.

For instance, if you use the included mailer.py script, you
can configure it so that commit e-mails for /project1/trunk
are sent to one address, and /project2/trunk to another

Robert Hunter
This communication, including any attachments, is confidential.
If you are not the intended recipient, you should not read it
- please contact me immediately, destroy it, and do not copy
or use any part of this communication or disclose anything about it,
Thank you.
Please note that this communication does not designate an information system
for the purposes of the Electronic Transactions Act 2002
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 22 23:31:19 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.