Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: infrastructure-dev@apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <49A81E33.2020905@apache.org>
Date: Fri, 27 Feb 2009 09:09:07 -0800
From: Paul Querna <pquerna@apache.org>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: infrastructure-dev@apache.org
Subject: Re: Project update scripts
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>
 <49A81654.90602@apache.org>
In-Reply-To: <49A81654.90602@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Grzegorz Kossakowski wrote:
> 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?
> 

Can't we can figure out what needs to be done, and just add another 
notification method to the post-commit hook?