This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Eliminating -mno-cygwin from gcc.


Yaakov (Cygwin Ports) wrote:
-----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.

The discussion has been to augment 'setup.exe' in a way as to provide users with feedback about "important" package changes in general. It has come up in the context of the gcc change but would have to apply generally. "Important" would be defined by the maintainer by some mechanism. Presumably, every release of package 'foo' does not trigger the "important" flag. ;-)

--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]