On Fri, Jan 06, 2012 at 02:45:15PM -0800, Junio C Hamano wrote:
quoted
Did you want to leave the parse_object optimization until next cycle,
too? It's not loosening checks, but it's such a core piece of code that
it makes me nervous somebody somewhere is abusing "struct object" in a
way that will break it.
I was just updating the "What's cooking" report and my current thinking is
that we should keep all three in "next" to give it a bit of exposure for
now, and merge them to "master" early in the 1.7.10 cycle.
That sounds perfect. Thanks.
-Peff