Re: [PATCH v2 3/5] manual: Add new header and standards annotations.

[Rical Jasan <ricaljasan at pacific dot net>]

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 <https://sourceware.org/cgi-bin/pdw/ps_form.cgi> 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