Well maybe I should explain better.
I create a directory called SVN. Then Underneath that I create 2
directories Personal and websites. These directories under SVN
correspond to physical directories on our development webserver. At this
point using TortoiseSVN I turned Personal and websites into fsfs
repositories, respectively.
Now what I did, which probably was a mistake, under Personal, created
individual directories for developers (physical directories, not
repository directories). Then I made those developer directories
repositories.
So yeah probably goofed setup. What I found interesting was that in the
developer repositories the hook files located in the hooks directory
under the developer would not fire, only the ones at the Personal level.
So is this normal behavior.
Thanks
Kevin
(still learning)
-Kevin Marino
----------------------
Webmaster - NeighborCare Technology Center
kevin.marino@neighborcare.com
410 895 0377
******************************************************************
This e-mail and any attachments may contain information which is
confidential, proprietary, privileged or otherwise protected by law. The
information is solely intended for the named addressee (or a person
responsible for delivering it to the addressee). If you are not the
intended recipient of this message, you are not authorized to read,
print, retain, copy or disseminate this message or any part of it. If
you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete it from your computer.
******************************************************************
-----Original Message-----
From: Travis [mailto:svn@castle.fastmail.fm]
Sent: Tuesday, March 22, 2005 11:29 PM
To: Robert Hunter
Cc: users@subversion subversion
Subject: Re: hooks in sub repositories
On Mar 22, 2005, at 4:27 PM, Robert Hunter wrote:
> 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.
Hmmm, you might be able to auto-mount your repos as an auto-versioning
repos via WebDAV and then create a working fsfs repos inside it. If it
doesn't work today, I imagine, based on mailing list reports by the
developers, that it would work without pretty easily on MacOS X when
Subversion 1.2 is released. And then you could mount that repos and
create another inside it. Repeat until the inefficiencies bring your
server to its knees.
I don't see how such a construction would be useful, but it's
interesting to think that it could work. (And it could be prevented
pretty easily too, if it were worth it, but I doubt it is.)
Of course, I don't think this is what the original poster meant at all.
Mr. Hunter's comments are probably much useful to Mr. Kevin than my
own musings. :-)
-Travis Pouarz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 25 15:35:20 2005