Hi Junio,
On 2015-01-21 10:17, Junio C Hamano wrote:
The documentation did not format well. Tentatively I added the
attached fix-up on top of the series before merging to 'pu'.
[...]
Sorry for that! I have to admit that I did not even build the documentation :-(
I incorporated your fixes
The documentation did not format well. Tentatively I added the
attached fix-up on top of the series before merging to 'pu'.
* The wildcard in fsck.* and receive.fsck.* may have made sense
back in v1 when the variables are unbounded set, but v2 fixes it
and we now have a known fixed set of
At the moment, the git-fsck's integrity checks are targeted toward the
end user, i.e. the error messages are really just messages, intended for
human consumption.
Under certain circumstances, some of those errors should be allowed to
be turned into mere warnings, though, because the cost of
3 matches
Mail list logo
