Re: What's cooking in git.git (Oct 2016, #05; Thu, 20)

From: Pranit Bauva <pranit.bauva@gmail.com>
Date: Oct 21, 2016, 15:28 UTC
Message-ID: <CAFZEwPPDcL_DLHiFpxYW+Pk71Hu7kjqVN3jcL7_jvceCyLLmHg@mail.gmail.com>
In-Reply-To: <alpine.DEB.2.20.1610211457030.3264@virtualbox>

Hey Johannes,

On Fri, Oct 21, 2016 at 6:38 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 6 quoted lines

> I am unfortunately still busy with trying to figure out what exactly makes
> t6030 hang on `pu` (seems it thinks stdin is a tty and just waits for an
> answer), and then trying to reduce that insane amount of time wasted on
> running, and waiting for, the test suite, and for unrelated reasons I'll
> have to go offline for the rest of the day, so I will most likely be
> unable to assist further with this.

My patch series [1] is recently merged into pu which changed a lot of things around "git bisect next" which I remember that you mention it somewhere else too but don't exactly recollect where. There were some *really* drastic changes and they are evident with my conversation with Junio. Maybe you could tell a little bit more about what's happening with t6030 so that even I could dig further.

Heads up: The changes in "git bisect next" were related to revision walking so you might want to check it out.

Sorry for any inconvenience caused by this series.

Regards, Pranit Bauva