From: Mike Galbraith <efault@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git 1.7.0.2
Date: Mon, 08 Mar 2010 04:51:21 +0100 [thread overview]
Message-ID: <1268020281.6298.5.camel@marge.simson.net> (raw)
In-Reply-To: <7vy6i3epg0.fsf@alter.siamese.dyndns.org>
On Sun, 2010-03-07 at 14:29 -0800, Junio C Hamano wrote:
> * "git bisect -- pathspec..." did not diagnose an error condition properly when
> the simplification with given pathspec made the history empty.
Would that be what led to this somewhat less than perfect tip bisection
result? I had to repeat, leaving off the pathspec, in order to bisect
to the troublesome commit.
b4dad12cdd22f61eb093d23f11a7b09620e53aba is the first bad commit
git bisect start '--' 'tools/perf'
# good: [64ba9926759792cf7b95f823402e2781edd1b5d4] Merge branch 'for-linus' of git://git.open-osd.org/linux-open-osd
git bisect good 64ba9926759792cf7b95f823402e2781edd1b5d4
# bad: [a8313ee914acb061cacb44d0884e448760e33392] Merge branch 'perf/pebs'
git bisect bad a8313ee914acb061cacb44d0884e448760e33392
# good: [eaa5eec739637f32f8733d528ff0b94fd62b1214] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp
git bisect good eaa5eec739637f32f8733d528ff0b94fd62b1214
# bad: [b9377fc0bf1cd0b7b494337eacf8ccf0f7b52e1f] Merge branch 'perf/probes'
git bisect bad b9377fc0bf1cd0b7b494337eacf8ccf0f7b52e1f
# bad: [318794793ce30dc7000ed6992f4f81f308ae3958] manual merge of linus
git bisect bad 318794793ce30dc7000ed6992f4f81f308ae3958
# good: [617f757a1b45395ca3b11b162138ce514afc5b29] Merge branch 'perf/core'
git bisect good 617f757a1b45395ca3b11b162138ce514afc5b29
# good: [c93025db5f6d093fd00e96fde8e47d5c791a03fd] Merge branch 'perf/core'
git bisect good c93025db5f6d093fd00e96fde8e47d5c791a03fd
# good: [eb3addcb8fe9b81f47ad0f14ed0ae220f18ae83b] Merge branch 'perf/urgent'
git bisect good eb3addcb8fe9b81f47ad0f14ed0ae220f18ae83b
# bad: [b4dad12cdd22f61eb093d23f11a7b09620e53aba] Merge branch 'core/iommu'
git bisect bad b4dad12cdd22f61eb093d23f11a7b09620e53aba
next prev parent reply other threads:[~2010-03-08 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 22:29 [ANNOUNCE] Git 1.7.0.2 Junio C Hamano
2010-03-08 3:51 ` Mike Galbraith [this message]
2010-03-08 5:13 ` Junio C Hamano
2010-03-08 5:55 ` Mike Galbraith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1268020281.6298.5.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.