Return-Path: Delivered-To: apmail-infrastructure-dev-archive@minotaur.apache.org Received: (qmail 83362 invoked from network); 27 Feb 2009 16:35:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Feb 2009 16:35:59 -0000 Received: (qmail 84540 invoked by uid 500); 27 Feb 2009 16:35:59 -0000 Delivered-To: apmail-infrastructure-dev-archive@apache.org Received: (qmail 84404 invoked by uid 500); 27 Feb 2009 16:35:58 -0000 Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: infrastructure-dev@apache.org Delivered-To: mailing list infrastructure-dev@apache.org Received: (qmail 84391 invoked by uid 99); 27 Feb 2009 16:35:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Feb 2009 08:35:58 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.86.168.183] (HELO mxout-08.mxes.net) (216.86.168.183) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Feb 2009 16:35:50 +0000 Received: from [192.168.0.125] (unknown [82.210.157.165]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id B570DD05AF for ; Fri, 27 Feb 2009 11:35:28 -0500 (EST) Message-ID: <49A81654.90602@apache.org> Date: Fri, 27 Feb 2009 17:35:32 +0100 From: Grzegorz Kossakowski User-Agent: Thunderbird 2.0.0.19 (X11/20081227) MIME-Version: 1.0 To: infrastructure-dev@apache.org Subject: Project update scripts (was: Re: Zone for hosting git clones at Apache) References: <510143ac0901210319x4075b2b3v63a03ed9b19e80c4@mail.gmail.com> <5c902b9e0901210801v1a559062xd8aeb1c7fb1a4def@mail.gmail.com> <75bda7a00901310433g684ac36la49989813fc5a4af@mail.gmail.com> <510143ac0902250231r748ddda8q51647f045d08d8ef@mail.gmail.com> <49A56D1F.9000601@apache.org> <510143ac0902260436w5317ad77l18d1a2c3924a631e@mail.gmail.com> <49A70B89.6050904@apache.org> <510143ac0902261400k1277fe40xd1c1fe9f3513b1a4@mail.gmail.com> In-Reply-To: <510143ac0902261400k1277fe40xd1c1fe9f3513b1a4@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Jukka Zitting pisze: >> Is it possible to subscribe to some notification list that notifies about >> any commit made into public part of our svn? If so I would like to >> subscribe to it and then I could experiment with writing such a script. > > I don't think we have that, but the existing per-project commit > mailing lists should be a good a source of example notifications. Yep. Good idea. The problem is that there is no 1-1 mapping between per-project notification list and actual projects in SVN. What I mean here is (for example) situation with Cocoon where we have standard layout for 2.1 and 2.2 versions of Cocoon but Cocoon 3.0 that is written from scratch is subproject with its own branches/tags/trunk layout. Thus we would have to either: 1. Update all projects associated with given e-mail address 2. extract the path of modified files and try to scan all .git/config files for matching paths The second way is totally automatic so no mapping between repositories and e-mail addresses has to be maintained but this way is much more tricky. Do we need this trickery or we are fine with first option? -- Best regards, Grzegorz Kossakowski