From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3451 invoked by alias); 15 Apr 2008 14:17:51 -0000 Received: (qmail 3435 invoked by uid 22791); 15 Apr 2008 14:17:50 -0000 X-Spam-Check-By: sourceware.org Received: from pool-72-74-94-32.bstnma.fios.verizon.net (HELO ednor.cgf.cx) (72.74.94.32) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 15 Apr 2008 14:17:32 +0000 Received: by ednor.cgf.cx (Postfix, from userid 201) id 6CD7F2B352; Tue, 15 Apr 2008 10:17:30 -0400 (EDT) Date: Tue, 15 Apr 2008 14:17:00 -0000 From: Christopher Faylor To: cygwin-apps@cygwin.com Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area Message-ID: <20080415141730.GA21313@ednor.casa.cgf.cx> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <4800AF02.DC1B3AF5@dessent.net> <20080412151515.GG23852@calimero.vinschen.de> <48013F76.4D6B8FFC@dessent.net> <20080413094246.GJ23852@calimero.vinschen.de> <20080413193513.GA13302@ednor.casa.cgf.cx> <20080414095628.GA4069@calimero.vinschen.de> <20080414143631.GB18398@ednor.casa.cgf.cx> <48041AC2.DA789E78@dessent.net> <20080415085515.GW23852@calimero.vinschen.de> <20080415090849.GZ23852@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080415090849.GZ23852@calimero.vinschen.de> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-04/txt/msg00213.txt.bz2 On Tue, Apr 15, 2008 at 11:08:49AM +0200, Corinna Vinschen wrote: >On Apr 15 10:55, Corinna Vinschen wrote: >> On Apr 14 20:02, Brian Dessent wrote: >>>Christopher Faylor wrote: >>>>Yes, I know. I just don't think it clarifies anything to put a "Red >>>>Hat" in the registry. >>> >>>I was thinking "Cygwin" would be better as well, but since it is >>>supposed to be a two-level heirarchy how about >>>"HK{LM,CU}\Software\Cygwin Project\Cygwin". It has always seemed to me >>>that we actively try to de-emphasize any association that Red Hat has >>>in the actual day-to-day operation of the project, other than owning >>>the copyrights and having their own commercial fork. Likewise with the >> >>Well, not exactly. I have done a lot of my 1.7 development lately on >>blessed Red Hat time. The IPv6 changes and the long path name support >>wouldn't be as progressed as they are if I hadn't got enough paid time >>to do them. I don't think that deserves to be ignored. > >Having said that, should we really rename the registry keys, what do we >do with the "Program Options" and the two "heap_foo" values? I'd like to keep the "Program Options" and nuke the "heap_foo" options. I also object to using "Red Hat" as the "owner" regardless of how much paid work you've been able to do. I think it sends an extremely mixed message for the public Cygwin project to be viewed as "owned" by Red Hat while we solicit donations to help with development on the Cygwin web site. I've been paid by a few companies to work on Cygwin and have been spent long hours tracking down bugs for them. Additionally, most of the work I have done for Cygwin in the past was done in my spare time even when I was a paid employee While I realize that you've spent quite a bit more time being paid by Red Hat to make ipv6 and long path names work, I don't think that necessarily translates into using Red Hat as the owner key in the registry. Also, given that this is a Windows project I have to wonder just how much Red Hat would desire to have their names in the Windows Registry. cgf