John Peacock <jpeacock@rowman.com> wrote on 05/20/2005 12:08:09 PM:
> kfogel@collab.net wrote:
> > Not at all. If the repository convention is to attach a special
> > property to each project directory, and have the hook code look for
> > that property, that's fine. Or whatever. Nothing about this system
> > requires that metadata be stored outside the repository...
>
> You're right; a sufficiently advanced hook script could query the
> repository for more information. Would we include an example script
> which would do this data-diving or expect that to be a lesson for the
> admin (I'm not being completely facetious)?
My feeling is that Subversion has to provide a script like this. Why?
Hosting providers. I do not believe that they generally provide users
with access to the hook scripts, and they are not going to want to be
constantly tweaking the script as needs change. By making a script that
is driven by properties it will allow a hosting provider to simply enable
the script and then let the repository owners control it by setting
properties.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 20 18:46:55 2005