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: Tue, 24 Apr 2001 20:18:38 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: GCC -mno-cygwin vs mingw32-gcc cross environment. Message-ID: <20010424201838.A16608@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <3AE5A72B DOT 27311 DOT BA042D AT localhost> <027501c0cd18$7619b7c0$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: <027501c0cd18$7619b7c0$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Wed, Apr 25, 2001 at 09:43:59AM +1000 On Wed, Apr 25, 2001 at 09:43:59AM +1000, Robert Collins wrote: >> Given the above...when I say branch, I am saying create a cvs branch >> that adds i686-pc-mingw32-gcc as a subset of Cygwin when Cygwins -mno- >> cygwin switch is used... > >I don't see how that will help. CVS branchs allow for concurrent >development. I.E. If I ask chris nicely he may give me a new branch on >cvs.sources.redhat.com for me to really push the pthread code ahead - >and it would only be needed if there where 3 or 4 folk all working on >the same project but we didn't want to break CVS HEAD at all. > >Please explain a little more clearly for me :] And for me. I don't know what CVS branches have to do with this discussion. cgf