From: Andreas Schwab Date: Mon, 14 Dec 2015 18:08:48 GMT Subject: Re: git bisect with temporary commits Message-ID: <87si34hphr.fsf@igel.home> In-Reply-To: <20151214163726.GY13519@tonks> Florian Bruhin writes: > Now when trying to say it's good (and forgetting to remove the > temporary commits), I get this: > > $ git bisect good > Bisecting: a merge base must be tested > [981e1093dae24b37189bcba2dd848b0c3388080c] still good and does not compile > > Is this intended behaviour? Shouldn't git either do a reset to the > commit we're currently bisecting, or warn the user as it was probably > unintended to add new commits? You should instead tell git that HEAD^ is good, since that is what git asked you to test. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."