Hi Junio,
On 2015-06-19 21:28, Junio C Hamano wrote:
Johannes Schindelin johannes.schinde...@gmx.de writes:
Some legacy code has objects with non-fatal fsck issues; To enable the
user to ignore those issues, let's print out the ID (e.g. when
encountering missingemail, the user might want to
That ... can be made ... was not my wish but more like the way the
code is structured it is possible for somebody to do such a thing
easily, well done compliment ;-)
The message names will have to be shown somewhere in the
documentation, and in Documentation/ we try to use camelCase to show
the
Some legacy code has objects with non-fatal fsck issues; To enable the
user to ignore those issues, let's print out the ID (e.g. when
encountering missingemail, the user might want to call `git config
--add receive.fsck.missingemail=warn`).
Signed-off-by: Johannes Schindelin
Johannes Schindelin johannes.schinde...@gmx.de writes:
Some legacy code has objects with non-fatal fsck issues; To enable the
user to ignore those issues, let's print out the ID (e.g. when
encountering missingemail, the user might want to call `git config
--add
4 matches
Mail list logo
