This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: PROPOSAL: Variation on an Alternate policy for obsoleting targets
- From: Paul Koning <pkoning at equallogic dot com>
- To: bkorb at veritas dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 19 May 2003 09:08:53 -0400
- Subject: Re: PROPOSAL: Variation on an Alternate policy for obsoleting targets
- References: <3EC7B977.16D969C@veritas.com>
>>>>> "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