From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 67767 invoked by alias); 8 Feb 2017 13:52:14 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 67750 invoked by uid 89); 8 Feb 2017 13:52:13 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=purely, adapting X-HELO: relay1.mentorg.com Date: Wed, 08 Feb 2017 13:52:00 -0000 From: Joseph Myers To: Rical Jasan CC: , , Subject: Re: [PATCH v2 3/5] manual: Add new header and standards annotations. In-Reply-To: Message-ID: References: <20161206105525.21117-1-ricaljasan@pacific.net> <20161206105525.21117-4-ricaljasan@pacific.net> <665e49d4-dfa0-e14d-a793-d4acdca8e617@pacific.net> <7dd6da88-601f-e6f2-1f16-c24d7fdf84e2@pacific.net> <8c01ffc4-fcee-d584-bfab-d74a0b552b77@pacific.net> <8e8b0d56-b001-1870-1b5c-9895a1301c07@pacific.net> <0d5758f3-52bb-31cb-21e2-d218ace98065@pacific.net> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2017-02/txt/msg00157.txt.bz2 On Wed, 8 Feb 2017, Rical Jasan wrote: > I'd envision a v3 containing patches for: > > 1. Introducing the @standards and related macros. > 2. Script(s) to generate the Summary and check annotations. > 3. Adding and converting annotations. I think any conversion to @standards should have the following property: there is a patch that changes all existing comment-based annotations to @standards-based annotations, leaving the generated summary and the whole of the formatted manuals unchanged after the patch. That patch should contain a small manually written patch (adapting the summary-generation script to read @standards instead of comments, adding dummy definitions of @standards macros), a script that does the conversion (which of course wouldn't be committed, just the results of running it would be), and a large purely automatically generated set of changes made by the conversion script. That is, there must not be an "Adding and converting annotations." patch; the automated conversion must be clearly separated from any patch that actually changes or adds any annotations to the manual. (This does not assert whether such changes and additions happen before or after the conversion.) -- Joseph S. Myers joseph@codesourcery.com