Re: [PATCH] Documentation/git-add.txt: Explain --patch option in layman terms

Jari Aalto [off-list ref] writes:

I could offer patches, but not in any time frame to do it in one-swoop
do-it-all patch. To distribute time and effort to do so, it would be
sensible to handle one manual at a time. The whole work would eventually
get done.

Yeah, that's the spirit, and that is why I said you do not necessarily
have to do all the work yourself.  It would be expected of that volunteer
to keep an eye on patches other helpful folks may send to cover the issue,
vet them to make sure they do not introduce silly typos, AsciiDoc
breakages, and needless conflicts.

As to guidelines, I think your "spell all top-level headlines in caps" is
a reasonable one, as "man" backend for AsciiDoc does that anyway.

For the ancient "Synopsis" issue, SD5-XCU-ERN-97 would be a reasonable
guideline to follow (http://www.opengroup.org/austin/docs/austin_325.txt).

There could be section in TODO.

    RFH - Request for help: Manual page adjustments

    - If you have some spare time, the following manual pages adjustment
      is needed for all git manuals ....

Or 2-weekly RFH post could announce the need. That would be one way to
coordinate participants.

I would leave such a procedural issue to the volunteer who heads the
effort to decide.  If you are asking me to decide, then you are not
volunteering yourself, but you are volunteering _me_ for the job ;-).

Thanks.