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: Thu, 21 Mar 2002 11:54:14 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: OT: possible project/research project Message-ID: <20020321165414.GP8437@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Thu, Mar 21, 2002 at 11:37:26PM +1100, Robert Collins wrote: > > >> -----Original Message----- >> From: Jesper Eskilson [mailto:jojo AT virtutech DOT se] >> Sent: Thursday, March 21, 2002 11:27 PM >> To: Robert Collins >> Cc: cygwin AT cygwin DOT com >> Subject: Re: OT: possible project/research project >> >> >> "Robert Collins" writes: >> >> > make -j serialises at directory borders (at a minimum). You might >> > like to review the 'recursive make considered harmful' >> paper (if you >> > haven't already). >> >> 'make -j' and recursive make are orthogonal issues. > >Depending on context, I agree. Can we take this discussion somewhere else? I don't really see how it relates to cygwin. I've already suggested that there are already shells around that do some of what you're proposing. I've already said that, regardless, it would be very unlikely that I will be interested in this for cygwin. Discussions about make -j, the awfulness of fork, etc. really don't have much bearing to cygwin. Please continue the discussion in private email. cgf -- Please do not send me personal email with cygwin questions. Use the resources at http://cygwin.com/ . -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/