This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc 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] |
On 04/18/2017 03:47 PM, Carlos O'Donell wrote:
(a) If your OS and machine port has build-many-glibcs.py support then all maintainers will strive to ensure that their changes do not break those OS and machine combinations supported by the script, and will work to correct any such past breakage.
I don't want to see running build-many-glibcs.py as a requirement for posting patches. The main reason for that is that it's rather expensive (either you need to be very patient, or you need a fairly big machine).
What do you think about of out-of-tree GCC ports? Can we support targets which are not included in any upstream GCC version, only patches on top of an upstream version which already fell out of support?
Thanks, Florian
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |