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 From: "Dave Korn" To: Subject: RE: Updated: inetutils-1.3.2-29 Date: Wed, 20 Apr 2005 16:52:25 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20050420153714.GH13412@trixie.casa.cgf.cx> Message-ID: X-OriginalArrivalTime: 20 Apr 2005 15:52:31.0175 (UTC) FILETIME=[F5EA7D70:01C545C0] ----Original Message---- >From: Christopher Faylor >Sent: 20 April 2005 16:37 > On Wed, Apr 20, 2005 at 04:27:00PM +0100, Dave Korn wrote: >> ----Original Message---- >>> From: Christopher Faylor >>> Sent: 20 April 2005 15:37 >> >>> On Wed, Apr 20, 2005 at 03:19:32PM +0100, Dave Korn wrote: >>>> I was planning to look into that for my next patch, as it happens! >>> >>> So were *you* under the impression that you needed a cygwin copyright >>> assignment to modify setup.exe? That's not the case, if so. >> >> Umm, no, I was (and still am) under the impression that I need a cygwin >> assignment on file for contributions to the dll. I hadn't actually >> considered what the case was for setup, although the phrase "As per >> cygwin1.dll:" (apps/setup/README) was somewhat suggestive. The terms >> for accepting contributions for both setup and newlib seem somewhat >> under-documented, or at least I couldn't find them explicitly stated >> anywhere. > > Well, I'm glad I could clear up your apparent misconception then. > > cgf A doco patch would be even nicer :) and save you the time and trouble in future, no doubt.... cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/