Re: [PATCH 14/18] fsck: allow upgrading fsck warnings to errors

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Dec 22, 2014, 22:01 UTC
Message-ID: <alpine.DEB.1.00.1412222259070.21312@s15462909.onlinehome-server.info>
In-Reply-To: <xmqq4mt3idho.fsf@gitster.dls.corp.google.com>

Hi Junio,

On Wed, 10 Dec 2014, Junio C Hamano wrote:

Show 8 quoted lines

> Johannes Schindelin <johannes.schindelin@gmx.de> writes:
> 
> > The 'invalid tag name' and 'missing tagger entry' warnings can now be
> > upgraded to errors by setting receive.fsck.invalid-tag-name and
> > receive.fsck.missing-tagger-entry to 'error'.
> 
> Hmm, why can't all warnings promotable to errors, or are the above
> two mentioned only as examples?

Those were the only ones that were always shown as warnings but never treated as errors.

There is a third one coming, as part of the patches that will let fsck warn about NTFS-incompatible file names, but I want to get this patch series integrated into git.git first.

Ciao, Dscho