X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: "Joe Smith" Subject: Re: Which list should cygwin development be discussed on ? Date: Sat, 1 Jul 2006 15:42:00 -0400 Lines: 24 Message-ID: References: <44A474CE.7090100@netbauds.net> <20060630011818.GD2154@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com "Christopher Faylor" wrote in message news:20060630011818.GD2154@trixie.casa.cgf.cx... > On Fri, Jun 30, 2006 at 01:48:14AM +0100, Darryl Miles wrote: >>Is my more technical discussion better put onto the cygwin-patches list >>? > > No. The mailing list descriptions really are accurate. If you don't > have a patch, then you shouldn't be sending email to cygwin-patches. > Most cygwin development discussion occurs on the main list or on cygwin-apps. Basically The general rule for cygwin apps appears to be that the first messgage in a thread has to be about creation of new packages, or discussions about packaging policy. (Also requests for uploads go to that list). Then the disussion can drift a little to more general cygwin development, but should still be in the context of a specific package. Also, discussion of the development of setup.exe usually takes place on cygwin-apps, because that is the designated list for discussing bugs in setup.exe -- 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/