Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 6 Jul 2003 01:00:11 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: CVS tag for releases? Message-ID: <20030706050008.GA19378@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <1057465850 DOT 567 DOT 44 DOT camel AT jwhiteh> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Sun, Jul 06, 2003 at 05:39:36AM +0100, Elfyn McBratney wrote: >On Sun, 5 Jul 2003, Jeremy White wrote: >>Forgive me if I have missed something blindingly obvious, but I cannot >>find a CVS tag to correlate to the 1.3.22-1 release of cygwin1.dll. I >>see one for cygwin-1-3-19-1 on some winsup/cygwin files. >> >>I was hoping to check out a 'stable' release from CVS, and I'd >>appreciate any guidance on this (or the paper bag, if I've missed the >>obvious). > >Christopher Faylor (the project manager) stopped tagging CVS for >releases after 1.3.21 . The source code for 1.3.22 is in the 'cygwin' >'src' package, available via setup.exe . BTW, 1.3.22 will be the last >"stable" release of the 1.3 series. Actually, I never (well, once, maybe) did a complete tag of the sources which would enable someone to build from scratch via cvs. -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam AT sourceware DOT org and be permanently blocked from mailing lists at sources.redhat.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/