PROPOSAL: Variation on an Alternate policy for obsoleting targets
Paul Koning
pkoning@equallogic.com
Mon May 19 13:15:00 GMT 2003
>>>>> "Bruce" == Bruce Korb <bkorb@veritas.com> writes:
Bruce> In the interests of keeping fixinc from becoming a
Bruce> monotonically increasing behemoth, I propose the following
Bruce> addition:
>> Now for the actual obsolescence rule. :-)
>>
>> Any target which has significant custom code (for instance, its
>> own subdirectory or file under config/) requires a maintainer.
>> This is most of them.
>>
>> Any such target without a maintainer is advertised as needing one.
Bruce> Maintainers would make at least one build with a
Bruce> GCC_MAINTAINER_MODE environment variable set.
Is there any documentation that explains what that does? I've only
seen statements that amount to "this does magical things that only
maintainer need".
paul
More information about the Gcc
mailing list