Return-Path: Delivered-To: apmail-httpd-apreq-dev-archive@www.apache.org Received: (qmail 32615 invoked from network); 22 Jun 2004 00:20:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 22 Jun 2004 00:20:18 -0000 Received: (qmail 18619 invoked by uid 500); 22 Jun 2004 00:20:37 -0000 Delivered-To: apmail-httpd-apreq-dev-archive@httpd.apache.org Received: (qmail 18541 invoked by uid 500); 22 Jun 2004 00:20:36 -0000 Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list apreq-dev@httpd.apache.org Received: (qmail 18448 invoked by uid 99); 22 Jun 2004 00:20:36 -0000 Received: from [218.214.6.102] (HELO beauty.rexursive.com) (218.214.6.102) by apache.org (qpsmtpd/0.27.1) with ESMTP; Mon, 21 Jun 2004 17:20:35 -0700 Received: from meowth.rexursive.com (meowth.rexursive.com [172.27.0.10]) by beauty.rexursive.com (Postfix) with ESMTP id 8E88F1E802; Tue, 22 Jun 2004 10:18:20 +1000 (EST) Received: from [172.27.0.20] (beast.rexursive.com [172.27.0.20]) by meowth.rexursive.com (Postfix) with ESMTP id B190FEFC0A; Tue, 22 Jun 2004 10:18:40 +1000 (EST) Subject: Re: libapreq2-2.04-dev snapshot + html docs From: Bojan Smojver To: Joe Schaefer Cc: APREQ List In-Reply-To: <87oencvfyu.fsf@gemini.sunstarsys.com> References: <87oencvfyu.fsf@gemini.sunstarsys.com> Content-Type: text/plain Organization: Rexursive Message-Id: <1087863963.2304.11.camel@beast.rexursive.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 22 Jun 2004 10:26:03 +1000 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Any chance this can end up in the distribution tarball too? Or do you prefer it if I do those only for the RPM releases? This is simply my selfish view of the things, of course, as I normally hammer the code on the train, with no network connection ;-) On Tue, 2004-06-22 at 06:00, Joe Schaefer wrote: > Future releases should include the API docs on the apreq > website, so please also look over the currrent generated docs > > http://cvs.apache.org/~joes/libapreq2-2.04-dev/docs/html/ -- Bojan