All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: git@vger.kernel.org
Subject: git bisect goes wild?
Date: Tue, 24 Feb 2009 19:44:14 +0100	[thread overview]
Message-ID: <20090224184414.GE22108@duck.suse.cz> (raw)

  Hi,

  I've been bisecting some change in Linux kernel. The output of
"git bisect log" is:
git-bisect start
# good: [bbf25010f1a6b761914430f5fca081ec8c7accd1] Linux 2.6.23
git-bisect good bbf25010f1a6b761914430f5fca081ec8c7accd1
# bad: [49914084e797530d9baaf51df9eda77babc98fa8] Linux 2.6.24
git-bisect bad 49914084e797530d9baaf51df9eda77babc98fa8
# bad: [fe071d7e8aae5745c009c808bb8933f22a9e305a] oom: add
# oom_kill_allocating_task sysctl
git-bisect bad fe071d7e8aae5745c009c808bb8933f22a9e305a
# good: [117494a1b65183f0e3fcc817b07944bc5c465050] Merge
# master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6
git-bisect good 117494a1b65183f0e3fcc817b07944bc5c465050
# bad: [419217cb1d0266f62cbea6cdc6b1d1324350bc34] Merge branch
# 'v2.6.24-lockdep' of
# git://git.kernel.org/pub/scm/linux/kernel/git/peterz/linux-2.6-lockdep
git-bisect bad 419217cb1d0266f62cbea6cdc6b1d1324350bc34
# good: [c8c55bcb43d790d97790cfa319d80045a71fde39] Merge
# git://git.infradead.org/mtd-2.6
git-bisect good c8c55bcb43d790d97790cfa319d80045a71fde39
# good: [3e9830dcabdeb3656855ec1b678b6bcf3b50261c] sched: run
# sched_domain_debug() if CONFIG_SCHED_DEBUG=y
git-bisect good 3e9830dcabdeb3656855ec1b678b6bcf3b50261c

  But after the last command, I was sent to commit
9ec76fbf7d6da3e98070a7059699d0ca019b0c9b which is far outside the window
between the last good and bad commit. How come? git version is 1.5.6.
  Thanks for any suggestions.

								Honza

PS: Please CC me since I'm not on the list.
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

             reply	other threads:[~2009-02-24 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 18:44 Jan Kara [this message]
2009-02-24 18:59 ` git bisect goes wild? Peter Harris
2009-02-24 19:10   ` Jan Kara
2009-02-24 19:14     ` Teemu Likonen
2009-02-24 19:28       ` Jan Kara
2009-02-24 19:46     ` Daniel Barkalow
2009-02-24 20:04       ` Jan Kara
2009-02-24 21:15         ` Daniel Barkalow

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=20090224184414.GE22108@duck.suse.cz \
    --to=jack@suse.cz \
    --cc=git@vger.kernel.org \
    /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.