fsck: document the new receive.fsck.<msg-id> options
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Johannes Schindelin committed
Jun 22, 2015 at 17:27 UTC
4b55b9b4793b2b134fb439161d5407168cd88dcc
1 file changed
+14
Documentation/config.txt
+14
@@ -2197,6 +2197,20 @@ receive.fsckObjects::
2197
Defaults to false. If not set, the value of `transfer.fsckObjects`
2198
is used instead.
2199
2200
+receive.fsck.<msg-id>::
2201
+ When `receive.fsckObjects` is set to true, errors can be switched
2202
+ to warnings and vice versa by configuring the `receive.fsck.<msg-id>`
2203
+ setting where the `<msg-id>` is the fsck message ID and the value
2204
+ is one of `error`, `warn` or `ignore`. For convenience, fsck prefixes
2205
+ the error/warning with the message ID, e.g. "missingEmail: invalid
2206
+ author/committer line - missing email" means that setting
2207
+ `receive.fsck.missingEmail = ignore` will hide that issue.
2208
++
2209
+This feature is intended to support working with legacy repositories
2210
+which would not pass pushing when `receive.fsckObjects = true`, allowing
2211
+the host to accept repositories with certain known issues but still catch
2212
+other issues.
2213
+
2214
receive.unpackLimit::
2215
If the number of objects received in a push is below this
2216
limit then the objects will be unpacked into loose object