Re: [PATCH v2 15/18] fsck: Document the new receive.fsck.* options.

> On Mon, Jan 19, 2015 at 10:51 AM, Johannes Schindelin
> <johannes.schindelin@gmx.de> wrote:
>> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
>> ---
>> diff --git a/Documentation/config.txt b/Documentation/config.txt
>> index ae6791d..7371a5f 100644
>> --- a/Documentation/config.txt
>> +++ b/Documentation/config.txt
>> @@ -2130,6 +2130,31 @@ receive.fsckObjects::
>>         Defaults to false. If not set, the value of `transfer.fsckObjects`
>>         is used instead.
>>
>> +receive.fsck.*::
>> +       When `receive.fsckObjects` is set to true, errors can be switched
>> +       to warnings and vice versa by configuring the `receive.fsck.*`
>> +       settings. These settings contain comma-separated lists of fsck
>> +       message IDs. For convenience, fsck prefixes the error/warning with
>> +       the message ID, e.g. "missing-email: invalid author/committer line
>> +       - missing email" means that setting `receive.fsck.ignore =
>> +       missing-email` will hide that issue.
>> ++
>> +--
>> +       error::
>> +               a comma-separated list of fsck message IDs that should be
>> +               trigger fsck to error out.
>> +       warn::
>> +               a comma-separated list of fsck message IDs that should be
>> +               displayed, but fsck should continue to error out.
>> +       ignore::
>> +               a comma-separated list of fsck message IDs that should be
>> +               ignored completely.
>> ++
>> +This feature is intended to support working with legacy repositories
>> +which would not pass pushing when `receive.fsckObjects = true`, allowing
>> +the host to accept repositories certain known issues but still catch
> 
> s/certain/with &/