Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Message-ID: <2693598.1191256130647.JavaMail.jira@brutus>
Date: Mon, 1 Oct 2007 09:28:50 -0700 (PDT)
From: "Travis Vitek (JIRA)" <jira@apache.org>
To: stdcxx-dev@incubator.apache.org
Subject: [jira] Reopened: (STDCXX-560) add ASL headers to all config tests
In-Reply-To: <10784532.1190077063672.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/STDCXX-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Travis Vitek reopened STDCXX-560:
---------------------------------

      Assignee: Travis Vitek  (was: Farid Zaripov)

Additional patch is required.

> add ASL headers to all config tests
> -----------------------------------
>
>                 Key: STDCXX-560
>                 URL: https://issues.apache.org/jira/browse/STDCXX-560
>             Project: C++ Standard Library
>          Issue Type: Sub-task
>          Components: Release
>    Affects Versions: trunk
>            Reporter: Martin Sebor
>            Assignee: Travis Vitek
>            Priority: Blocker
>             Fix For: 4.2
>
>         Attachments: compiler-config.patch, config-tests.patch, configure.patch, missed-config.patch
>
>
> According to the ASF Source Header and Copyright Notice Policy (http://www.apache.org/legal/src-headers.html), all human-readable Apache-developed files that are included within a distribution must include ASL header text. None of the source files for our config tests currently does. These headers need to be added in time for the 4.2.0 release.
> Note that since in the config tests, the first line is reserved for the "label" displayed by GNUMakefile.cfg before compiling the test, the headers cannot start on the first line. Instead, it should be fine to append the header to the end of every config test instead.
> Since the above mentioned policy applies to releases distributed after November 1, 2006, this task affects trunk only (and not any already published releases or snapshots).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.