Re: What's cooking in git.git (Apr 2015, #02; Tue, 14)

[Johannes Schindelin <johannes.schindelin@gmx.de>]

Hi Junio,

On 2015-04-14 23:49, Junio C Hamano wrote:
> 
> * jc/update-instead-into-void (2015-04-01) 1 commit
>   (merged to 'next' on 2015-04-08 at 8ef4e15)
>  + push-to-deploy: allow pushing into an unborn branch and updating it
> 
>  A push into an unborn branch, with "receive.denyCurrentBranch" set
>  to "updateInstead", did not check out the working tree as expected.

Thank you for cleaning up after me.

> * js/fsck-opt (2015-01-21) 19 commits
>  - fsck: support ignoring objects in `git fsck` via fsck.skiplist
>  - fsck: git receive-pack: support excluding objects from fsck'ing
>  - fsck: introduce `git fsck --quick`
>  - fsck: support demoting errors to warnings
>  - fsck: document the new receive.fsck.* options
>  - fsck: allow upgrading fsck warnings to errors
>  - fsck: optionally ignore specific fsck issues completely
>  - fsck: disallow demoting grave fsck errors to warnings
>  - fsck: add a simple test for receive.fsck.*
>  - fsck: make fsck_tag() warn-friendly
>  - fsck: handle multiple authors in commits specially
>  - fsck: make fsck_commit() warn-friendly
>  - fsck: make fsck_ident() warn-friendly
>  - fsck: report the ID of the error/warning
>  - fsck: allow demoting errors to warnings via receive.fsck.warn = <key>
>  - fsck: offer a function to demote fsck errors to warnings
>  - fsck: provide a function to parse fsck message IDs
>  - fsck: introduce identifiers for fsck messages
>  - fsck: introduce fsck options
> 
>  "fsck.warnings = <list of error tokens>" I suggested turned out to
>  be an unpopular choice (sorry Dscho).
> 
>  Expecting a reroll.

Yeah, I'll get to this either today or tomorrow.

Sorry for the long wait,
Dscho