On Mon, Feb 06, 2017 at 12:49:34PM -0800, Junio C Hamano wrote:
> Of course, that will make it easier to let broken objects created by
> newer reimplementations of Git (and bugs in our code that cause us
> to create such broken objects) go unnoticed, so we would want to
> keep them at warn (not ignore) for the end-users.
Yes, sorry if that wasn't clear. By "loosen" I just meant to warn,
not ignore.
So a viable path forward is perhaps:
1. Add fetch.fsck.* (and probably transfer.fsck.*) to match the
receive-pack options.
2. Go over the current list of default warning/error settings and make
sure they are sensible.
3. Add a "light" mode to transfer.fsckObjects and friends that blocks
only errors, not warnings. Maybe setting the config bool to
"errors-only" instead of "true" or something.
4. (Optional) Default transfer.fsckObjects to "errors-only".
The escape hatch is to set fsckObjects to "false", or to downgrade
your specific problem to a warning via transfer.fsck.*.
-Peff