Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 9927 invoked by uid 500); 16 May 2003 12:48:20 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 9893 invoked from network); 16 May 2003 12:48:19 -0000 Received: from anchor-post-35.mail.demon.net (194.217.242.85) by daedalus.apache.org with SMTP; 16 May 2003 12:48:19 -0000 Received: from media.demon.co.uk ([80.177.14.141]) by anchor-post-35.mail.demon.net with esmtp (Exim 3.36 #2) id 19GedH-0001nq-0Z for cocoon-dev@xml.apache.org; Fri, 16 May 2003 13:48:19 +0100 Date: Fri, 16 May 2003 13:48:17 +0100 Subject: Re: No mailinglist for cocoon-site-cvs Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: Jeremy Quinn To: cocoon-dev@xml.apache.org Content-Transfer-Encoding: 7bit In-Reply-To: <3EC4D74F.3000602@apache.org> Message-Id: X-Mailer: Apple Mail (2.552) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Friday, May 16, 2003, at 01:19 PM, Nicola Ken Barozzi wrote: > > Carsten Ziegeler wrote, On 16/05/2003 14.15: > >> Hi, >> it seems that the commit messages for cocoon-site should go to >> the cocoon-site-cvs mailing list. I guess from the message below >> that this list does not exist. >> We could either create it or just sent all messages to cocoon-cvs >> for now. What do you think? > > What about using cocoon-docs? We already get the traffic of the Wiki, > and in this way it's easier to coordinate the two efforts. As well as > making all subscribe to that list ;-) I find the RSS feed from the Wiki to be a convenient and unobtrusive way of keeping up to date with changes there. regards Jeremy