Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Fri, 5 Jan 2001 00:04:48 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: Squid Message-ID: <20010105000448.A4499@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <03e901c07645$855d0220$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <03e901c07645$855d0220$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Thu, Jan 04, 2001 at 10:57:31PM +1100 On Thu, Jan 04, 2001 at 10:57:31PM +1100, Robert Collins wrote: >Chris, >I have a squid tarball that will shortly follow the contribution >checklist... how do I go about getting it on the ftp server for >copying to the mirrors/allowing user testing? I've created a /sourceware/ftp/anonftp/pub/cygwin/contrib directory on sources.redhat.com. Is is owned by you so you can upload the binary and source tarballs there yourself. If you want to label this as a test release, you should also put a "setup.hint" file in that directory with something like: test x.y.z in it. Where x.y.z is the version number. cgf