Re: What's cooking in git.git (Nov 2013, #05; Thu, 21)

From: Vicent Martí <tanoku@gmail.com>
Date: Nov 22, 2013, 19:47 UTC
Message-ID: <CAFFjANQy72zLuxtpA+-nMhYEt=qfOu_FSszR8X7QNPTKBEi6tA@mail.gmail.com>
In-Reply-To: <xmqq61rk1b52.fsf@gitster.dls.corp.google.com>

On Fri, Nov 22, 2013 at 8:36 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 12 quoted lines

>> Do we want to try this in 'next' post-1.8.5, or should I try to prod an
>> area expert like Shawn into doing another round of review?
>
> Yes ;-).
>
> I recall starting to read the series over and then got sidetracked
> in the middle and never finishing.  I'll try to make time sometime
> this weekend (we are still buried in boxes after the move, though,
> so no promises) myself.
>
> How close is this what you guys are running in production these
> days, by the way?

We are running a slightly older version of the patchset, because we're still on 1.8.4 and the current reroll doesn't apply cleanly there.

If this could make it to `next` some time next week, that would work out great for us, because we may start considering using `next` as a partial or full deployment on our production machines

This also means that we could exercise the patchset and everything else that is queued up in next release... You must remember all the corner cases and bugs peff brings to the list every time we deploy a new Git to production. Wouldn't it be nice to have a thorough checking of the current iteration *before* the release, and not after? :)

*hint hint*