From users-return-2497-daniel=haxx.se@subversion.apache.org Wed May 5 01:43:37 2010 Return-Path: Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by giant.haxx.se (8.14.3/8.14.3/Debian-9) with SMTP id o44NhZYO009805 for ; Wed, 5 May 2010 01:43:36 +0200 Received: (qmail 92180 invoked by uid 500); 4 May 2010 23:43:37 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 92173 invoked by uid 99); 4 May 2010 23:43:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 23:43:37 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_FRT_ADULT2 X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of qazwart@gmail.com designates 209.85.221.178 as permitted sender) Received: from [209.85.221.178] (HELO mail-qy0-f178.google.com) (209.85.221.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 23:43:31 +0000 Received: by qyk8 with SMTP id 8so6189585qyk.4 for ; Tue, 04 May 2010 16:43:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=n+v+uOmj5lL8hdqywBuFWOR3ezawxz3IP27C17Psagk=; b=jko8KvLHIuG3ZUxA/xxk2dA8r1rjG4w5+SrvxJUbhWdVMq0lwIHiDtNcniKGfCZLXN DNB8W758v3zsFVcgSM/tzqywzHJVyS4jLDdGBHOr9mFJm3G68Te9obrWq2PmG1HpOizb JsTxKFY5gUxEi8ZAYW6fjcdgd3qUc9fOueO1Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=UXbnD12Ck5wd47jh3L21ICyMAcyXSjp51gC9uLIfYitQEu10f6hEcv14UZqky9vfcF BJcC09yb/qjUS3uySi1pXL40VSogFBp7HCmzHhqlnztFgtbz50b+UNgJAHf4DvTYBId3 NDP5d36c3Q7hdrlvpc853ybYFgEelyfPRO7yw= MIME-Version: 1.0 Received: by 10.224.127.5 with SMTP id e5mr6010202qas.1.1273016588513; Tue, 04 May 2010 16:43:08 -0700 (PDT) Received: by 10.224.2.67 with HTTP; Tue, 4 May 2010 16:43:08 -0700 (PDT) In-Reply-To: References: Date: Tue, 4 May 2010 19:43:08 -0400 Message-ID: Subject: Re: Hooks scripts Merge, Reintegrate, and similar From: David Weintraub To: =?ISO-8859-2?B?Vm9q4ehlayBBbGW5?= Cc: "users@subversion.apache.org" Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org 2010/5/4 Voj=E1=E8ek Ale=B9 : > Hi all, > Is it possible to decide and log out, that new Branch was created, branch= e was reintergrated, tag was created using any of svn hooks? Hooks don't run in the user's environment and therefore cannot talk to the user who did the commit or lock or whatever triggered the hook. The hook script cannot do anything with the client's workspace either. The best you can do is email the user or if the hook fails, send to STDERR something that the user will see. If what you want is an email to someone when someone creates a branch or does some sort of merge, that's sort of possible. What you have to do is have a hook script that can help determine that information. You'd have to have some way of examining the Subversion log and parsing the information you need. Branching might be fairly easy since it is a copy and you expect branches to be copied to a particular place in your repository. For example: A /modules/adsuite/branches/5.3.3.5 (from /modules/adsuite/tags/DEV/ADS-5.3.3-D-1292:64049) I can see that branch 5.3.3.5 was created from tag ADS-5.3.3-D-1292. But, only because I see that the directory was copied to under the branches directory. Merging is a bit harder to figure out since the log itself just shows the files that were changed, and doesn't show a change in the svn:merge property. However, I guess you could get a list of all the files changed, then compare the svn:merge properties and see which got changed (which would show you that it was merged). > Another question is about, how to get enough information using svnlook bu= t with no impacting performance of operations of svn server. What I mean is= , that if I will use svnlook changed [rep] command on large commit (say 100= + files in one commit) if it will not extremely impact performens of svn se= rver. svnlook is very efficient. I have no problems with running svnlook on large number of changes. However, what you do with that information might impact the server if you do very program intensive stuff with it. --=20 David Weintraub qazwart@gmail.com