delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/08/16/14:16:55

X-Spam-Check-By: sourceware.org
Date: Wed, 16 Aug 2006 14:17:09 -0400
From: Bob Rossi <bob_rossi AT cox DOT net>
To: cygwin AT cygwin DOT com
Subject: Re: change in behavior of make from 3.80 to 3.81
Message-ID: <20060816181709.GB7538@brasko.net>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060815151104 DOT 0b40e260 AT pop DOT nycap DOT rr DOT com> <01b901c6c116$21259430$a501a8c0 AT CAM DOT ARTIMI DOT COM> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816091525 DOT 0ab90af0 AT pop DOT nycap DOT rr DOT com> <20060816144110 DOT GX20467 AT calimero DOT vinschen DOT de> <20060816174406 DOT GA7538 AT brasko DOT net> <20060816180659 DOT GA5064 AT trixie DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
In-Reply-To: <20060816180659.GA5064@trixie.casa.cgf.cx>
User-Agent: Mutt/1.5.11
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

> >I think your solution is well stated.  Does anyone know who was
> >maintaining the old patch to make, so that a discussion with that
> >person could be made more substantial on a technical level?
> 
> And ^^^this^^^ is a perfect example of why this discussion is so
> frustrating.
> 
> Does someone *really* have to tell you who was "maintaining the old
> patch"?  If you really need to be told this then you really don't have
> the right to an opinion on this subject at all since you clearly haven't
> been paying any attention.

I think you are all to knowledgable about cygwin and should step back
and think about people that use Cygwin as a black box and understand
absolutly nothing about it or it's development process. The frustration
you are expressing is understandable to me. However, with a little
managerial effort on your part, you could use your knowledge (if you so 
choose) to help the rest of us organize a productive way to develop a
patch to the upstream make. I thought Corinna spoke very well on this
matter, and is why I even bothered responding to this list.

Bob Rossi

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019