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

2014-12-22 Thread Johannes Schindelin
Hi Junio, On Mon, 22 Dec 2014, Junio C Hamano wrote: > Johannes Schindelin writes: > > > On Wed, 10 Dec 2014, Junio C Hamano wrote: > > > >> Johannes Schindelin writes: > >> > >> > The 'invalid tag name' and 'missing tagger entry' warnings can now be > >> > upgraded to errors by setting recei

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

2014-12-22 Thread Junio C Hamano
Johannes Schindelin writes: > Hi Junio, > > On Wed, 10 Dec 2014, Junio C Hamano wrote: > >> Johannes Schindelin 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-ta

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

2014-12-22 Thread Johannes Schindelin
Hi Junio, On Wed, 10 Dec 2014, Junio C Hamano wrote: > Johannes Schindelin 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'

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

2014-12-10 Thread Junio C Hamano
Johannes Schindelin 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 o

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

2014-12-08 Thread Johannes Schindelin
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'. Incidentally, the missing tagger warning is now really shown as a warning (as opposed to being reported with the "erro