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

Re: Checkout hooks?

From: Adrian Hoe 贺文耀 <mailbox_at_adrianhoe.com>
Date: 2006-03-24 16:12:15 CET

Yes! That's a positive attitude and I believe someone out there will
find this useful.

Does it work with 1.2.x?

On Mar 24, 2006, at 11:00 PM, Mathias Weinert wrote:

> Adrian Hoe wrote:
>> On Mar 24, 2006, at 12:34 AM, Ryan Schmidt wrote:
>>> On Mar 23, 2006, at 16:01, Adrian Hoe ??? wrote:
>>>> Is there any svn checkout hooks? I am interested to know who
>>>> checkout what at when.
>>> There is no checkout hook. However, perhaps the high-level apache
>>> access log will help you. It's available as of the Subversion 1.3
>>> version of the apache2 module and is described here:
>>> http://subversion.tigris.org/svn_1.3_releasenotes.html#dav-logging
>> Sorry for being vague. I want to be alerted by emails when someone
>> checkout something. Going through a log on apache is not so
>> convenient and take quite some time to do so,
>> Like post commit hooks, I can set who to be alerted on which
>> repository.
>> I went through svn manual, faq and website again and found nothing. I
>> believe it is not difficult to develop a checkout hook since there is
>> a post commit hook there.
>> Does anyone find this useful when administering/monitoring svn?
> You may want to look at
> http://svn.haxx.se/dev/archive-2006-02/0304.shtml
> and a little follow-up discussion in a separate thread for which
> I don't have the number available at the moment (the subject
> is "Re: [PATCH] pre-update and pre-getfile hook").
> Mathias

"If you missed the rising sun and the morning dew, don't miss the  
beautiful sunset." -- Adrian Hoe inspired by Michal Nowak, June 15 2004
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 24 16:13:20 2006

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.