X-Spam-Check-By: sourceware.org Message-ID: <45C6A793.8020008@users.sourceforge.net> Date: Sun, 04 Feb 2007 21:42:11 -0600 From: "Yaakov (Cygwin Ports)" User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Eliminating -mno-cygwin from gcc. References: <020d01c748b4$62d8b170$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <20070205030939 DOT GB24653 AT trixie DOT casa DOT cgf DOT cx> <45C6A0DC DOT 3010104 AT users DOT sourceforge DOT net> <20070205033101 DOT GE24653 AT trixie DOT casa DOT cgf DOT cx> In-Reply-To: <20070205033101.GE24653@trixie.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Christopher Faylor wrote: > If you have been reading this list for any length of time then it should > be obvious that merely mentioning something in cygwin-announce is not an > adequate way to let people know about serious changes. Trust me I know; my question is why this is being handled differently than other major changes (e.g. bash), or if you're looking for a new way in general of notification, particularly as carrying out the change will confuse much fewer people than leaving the status-quo. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFxqeTpiWmPGlmQSMRCJejAJ0az/++k76Qz3EekXatKVT/DuVpFgCgnA7R OXjMlOmmDVQskJhnj/CYSIo= =xUq/ -----END PGP SIGNATURE----- -- 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/