From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37454 invoked by alias); 15 Dec 2016 09:58:20 -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 37432 invoked by uid 89); 15 Dec 2016 09:58:19 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=glibcgit, passage, you! X-HELO: mail.pacific.net Subject: Re: [PATCH v2 3/5] manual: Add new header and standards annotations. To: Joseph Myers 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> Cc: libc-alpha@sourceware.org, mtk.manpages@gmail.com, carlos@redhat.com From: Rical Jasan Message-ID: <8e8b0d56-b001-1870-1b5c-9895a1301c07@pacific.net> Date: Thu, 15 Dec 2016 09:58:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <8c01ffc4-fcee-d584-bfab-d74a0b552b77@pacific.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Null-Tag: ce4e6f0bb9f0ed76062da41cbdb06469 X-SW-Source: 2016-12/txt/msg00538.txt.bz2 On 12/14/2016 03:30 PM, Rical Jasan wrote: > On 12/14/2016 10:18 AM, Joseph Myers wrote: >> On Mon, 12 Dec 2016, Rical Jasan wrote: >>> On 12/08/2016 06:02 AM, Joseph Myers wrote: >>>> On Wed, 7 Dec 2016, Rical Jasan wrote: >>>> >>>>>> I think the approved pieces should be committed to reduce the size of the >>>>>> patch in future revisions. >>>>> >>>>> That would be for someone other than myself to handle, correct? Then, >>>> >>>> I'm assuming you have commit access and will commit approved patches, or >>>> pieces of patches that make sense on their own. >>> >>> I don't think I have commit access; I've never committed anything thus >>> far, at least. What do I need to get that process started? On the >>> wiki, I see a page for a Committer's Checklist, but that isn't about >>> becoming a committer. >> >> Please complete and name >> me as approver. > > Completed the form. Received notice my account was set up. Thank you! Am currently reviewing the wiki, particularly GlibcGit. (I see on MAINTAINERS I could have found the form under "Becoming a maintainer (developer)"... that should probably be a rite of passage hahah) To confirm the approved pieces for once I'm prepared to push the commit button, were you referring to only the chapters so far in this patch ([v2 3/5] {argp,arith,lang,string}.texi) or also the first two (patches)? [v2 1/5] has been OK'd, no other comments; [v2 2/5] also was, though a typo was pointed out in the commit message. On the topic of commit messages, How would you like me to write them if this patch goes in piecewise? Should the first one look how I submitted it in this patch and subsequent patches can refer back to it or duplicate it? Or should they be rewritten to be more specific for each commit (maybe if committed by file)? Excited, Rical