Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 83178 invoked from network); 6 Nov 2003 23:36:23 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 6 Nov 2003 23:36:23 -0000 Received: (qmail 23833 invoked by uid 500); 6 Nov 2003 23:36:05 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 23799 invoked by uid 500); 6 Nov 2003 23:36:05 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 23770 invoked from network); 6 Nov 2003 23:36:05 -0000 Received: from unknown (HELO ms-smtp-03-eri0.southeast.rr.com) (24.25.9.102) by daedalus.apache.org with SMTP; 6 Nov 2003 23:36:05 -0000 Received: from noel770 (cae88-16-024.sc.rr.com [24.88.16.24]) by ms-smtp-03-eri0.southeast.rr.com (8.12.10/8.12.7) with SMTP id hA6Na9ZO010839 for ; Thu, 6 Nov 2003 18:36:09 -0500 (EST) From: "Noel J. Bergman" To: "Jakarta Commons Developers List" Subject: RE: [hivemind] what exactly is the issue here? Date: Thu, 6 Nov 2003 18:36:05 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal In-Reply-To: <6179B159-10A9-11D8-8DEF-003065DC754C@blueyonder.co.uk> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > is there any chance that the hivemind development team will voluntarily > 'cvs remove' the offending material ASAP�until the IP issues are sorted > out? That seems a bit drastic, considering the fact that Howard indicates that WebCT is prepared to contribute the code. No need to tear everything down and lose the CVS history. If necessary (and I don't know if it is), we could block access to the directory tree on the server pending resolution. Howard's information to the PMC would go a long way to informing you if any action at all is necessary. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org