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

From: Jari Aalto <jari.aalto@cante.net>
Date: Aug 31, 2009, 07:06 UTC
Message-ID: <873a78a2dc.fsf@jondo.cante.net>
In-Reply-To: <7vr5usyj3i.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 10 quoted lines

> Jari Aalto <jari.aalto@cante.net> writes:
>
>> I think the convention used in git's manual pages deviate from the
>> standard practise. We could make the git manual pages into line of:
>>
>> - write all the first level headings in all caps: "HEADING LIKE THIS"
>> - write second level heading: start Upper-lower: "Heading like this"
>>
>> Cf. rsync(1), ssh(1) etc. many pages prior git's existense.
>

[URL: That's a separate issue. The resolution hung in the air how to proceed]

Please be patient. I understand that you have lot work. I do care, therefore I take the time to suggest some chnages.

> Are you volunteering to coordinate such a change (in other words, you do
> not necessarily have to do _all_ the work yourself, alone)

We need resolution first. What would you think about that change?

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.

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.

Jari