From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Garber Subject: Re: Why can't I use git-bisect to find the first *good* commit? Date: Mon, 28 Mar 2011 15:12:25 -0400 Message-ID: References: <4D909DD1.2050904@viscovery.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Matthieu Moy , Johannes Sixt , =?UTF-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= , Git Mailing List To: demerphq X-From: git-owner@vger.kernel.org Mon Mar 28 21:12:54 2011 Return-path: Envelope-to: gcvg-git-2@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Q4Hrx-0000pz-P9 for gcvg-git-2@lo.gmane.org; Mon, 28 Mar 2011 21:12:54 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755274Ab1C1TMr (ORCPT ); Mon, 28 Mar 2011 15:12:47 -0400 Received: from mail-ew0-f46.google.com ([209.85.215.46]:38397 "EHLO mail-ew0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754721Ab1C1TMq (ORCPT ); Mon, 28 Mar 2011 15:12:46 -0400 Received: by ewy4 with SMTP id 4so1279608ewy.19 for ; Mon, 28 Mar 2011 12:12:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type; bh=im3gEOor2pCatSLoor6hXgBR4mOZcGWB6au3vIIQjWs=; b=QoHmvTc4VejzIXwo3nWx7+aC59qW9OF6xlJlrrLHOh/6obx4sNJ6wWwVJ4KtCr7W5y ulGGnbiiFDSOp1fU334ZCCK9Vc4EDv+qI4lpZ+jC/yzFq+be2zQ13Pc6n3r1Qx7rsg24 ySNC3q60ClfLyJ/2/oiktsWxO8bGbfRi++lqk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=XvBcc7GpaZOnuO4C4d30TSwJc82iln0wpKuQreRUkDylkFMRhCRpStzN7I+Pbr9cWS O/MSFyCtxP2jxFdPtTL1HDrtUJGT4lD/wPCDOkbTtvYngHXOmVGTgO5NvTmuQUoc1EQq Bj+0Gj5Gp3CxbRVls739Of+jpd/pJLr0VCnNs= Received: by 10.213.26.152 with SMTP id e24mr2005641ebc.125.1301339565169; Mon, 28 Mar 2011 12:12:45 -0700 (PDT) Received: by 10.213.105.76 with HTTP; Mon, 28 Mar 2011 12:12:25 -0700 (PDT) In-Reply-To: X-Google-Sender-Auth: uGSsFgVY76F1jMP3Sp45fPlLUjg Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: >> What is the point is finding manually a commit *on the same branch* when >> the tool can do that for you? > Seems to me that this is trying to cram two questions into one: > > A) where did branch foo diverge from branch bar and > B) which commit between that ancestor and bar did things break. To find the answer to A, I generally just do this (using an alias): git log --graph --oneline --all It takes at most a couple of seconds... hardly what I'd call a manual process.