Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 86866 invoked from network); 14 Oct 2004 13:16:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 14 Oct 2004 13:16:03 -0000 Received: (qmail 79640 invoked by uid 500); 14 Oct 2004 13:15:59 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 79407 invoked by uid 500); 14 Oct 2004 13:15:57 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 79379 invoked by uid 99); 14 Oct 2004 13:15:57 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [81.209.148.130] (HELO dd2020.kasserver.com) (81.209.148.130) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 14 Oct 2004 06:15:55 -0700 Received: from [192.168.20.145] (unknown [81.2.149.2]) by dd2020.kasserver.com (Postfix) with ESMTP id 5DD7A13DFC1; Thu, 14 Oct 2004 15:15:52 +0200 (CEST) Message-ID: <416E7CBC.20307@apache.org> Date: Thu, 14 Oct 2004 15:18:52 +0200 From: Torsten Curdt User-Agent: Mozilla Thunderbird 0.8 (X11/20040923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Cc: infrastructure@apache.org Subject: Re: [RT] subversion pre commit hook References: <416A5F6E.2020900@apache.org> <9CA85E48-1B6F-11D9-98C6-000A95AF004E@apache.org> <416BBC51.2060000@apache.org> <1097749922.4210.9411.camel@ighp> In-Reply-To: <1097749922.4210.9411.camel@ighp> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > I too am concerned about the different granularity. > > >>where is the problem? >> >>do one commit without the magic >>words and one with them. not >>*all* changes have to go into >>the status file. > > > Would you please explain this. I don't get it. ok :-) You can commit as usual ...it does not do anything to the status.xml at all. But if the commit messages starts with a specific word/header like: ---->8------------------- status: fixes-bug: 2314 due-to: someone@whatever.com message ---->8------------------- the parsing could be triggered. The parser will extract the key-value pairs fixes-bug=2314 due-to=someone@whatever.com and the message itself. This information will then be inserted as a xml fragment into our status.xml. But I am not sure how/if we can easily include this change into the same commit transaction. That's why I was hoping someone else has already played with subversion commit hooks. Since this does not seem to be the case I also CCed infrastructure. Maybe someone over there knows... > I don't have trouble editing status.xml when needed > but i am interested in your ideas. There are probably > many occasions where each of us has forgotten to add > an important entry to status.xml and so your solution > might help. I think it will help us a lot to keep the status file up to data. cheers -- Torsten