Re: What's cooking in git.git (Apr 2017, #04; Wed, 19)

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 25, 2017, 06:52 UTC
Message-ID: <xmqqa875uggj.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <3bd4a2d7-ada9-6198-8cf1-573d80cae1b4@kdbg.org>

Johannes Sixt <j6t@kdbg.org> writes:

Show 8 quoted lines

> The idea of marking git-gui and gitk histories that none of their
> commits is checked out: it erases all Git source code from the working
> directory, and a later bisection step places all code back and it
> requires a full build. Not a big deal with Git, but there are much
> larger code bases.
>
> The current bisect behavior makes this idea unworkable. For me, it was
> a big step backwards when it was implemented. :-(

I think it is sort-of unfair to blame bisect for that. It talks more about how "coolest merge evar!" cross project merges are unworkable in practice. With a proper submodule support, nobody should be doing it, but we started the cross project merge way before we had submodules, so...