Re: What's cooking in git.git (Apr 2019, #05; Thu, 25)

From: Taylor Blau <me@ttaylorr.com>
Date: Apr 26, 2019, 05:05 UTC
Message-ID: <20190426050531.GA7854@Taylors-MBP.hsd1.wa.comcast.net>
In-Reply-To: <xmqqsgu6wfv9.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Thu, Apr 25, 2019 at 07:15:06PM +0900, Junio C Hamano wrote:

Show 15 quoted lines

> * tb/unexpected (2019-04-10) 7 commits
>   (merged to 'next' on 2019-04-25 at c49927fca0)
>  + rev-list: detect broken root trees
>  + rev-list: let traversal die when --missing is not in use
>  + get_commit_tree(): return NULL for broken tree
>  + list-objects.c: handle unexpected non-tree entries
>  + list-objects.c: handle unexpected non-blob entries
>  + t: introduce tests for unexpected object types
>  + t: move 'hex2oct' into test-lib-functions.sh
>
>  Code tightening against a "wrong" object appearing where an object
>  of a different type is expected, instead of blindly assuming that
>  the connection between objects are correctly made.
>
>  Will merge to 'master'.

Thanks for picking this up. Before you merge to master, I want to make sure that the whole series was taken in.

I can see the first four of these landed on 'next' (in 5c07647d98...b49e74eac4), but I'm having some difficulty finding the later three.

Did you pick these up as well?

Thanks, Taylor