From: "N.P.S. N.P.S." <napohybelskurwysynom2010@gmail.com>
To: "Paweł Sikora" <pluto@agmk.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: git bisect selects commit outside initial bisect range?
Date: Mon, 27 Sep 2010 21:26:53 +0200 [thread overview]
Message-ID: <AANLkTinCL--ndP3bbATGU46V8VJLs5hOWC++jbsodBiB@mail.gmail.com> (raw)
In-Reply-To: <201009272051.33882.pluto@agmk.net>
Hi,
W dniu 27 września 2010 20:51 użytkownik Paweł Sikora <pluto@agmk.net> napisał:
> hi,
>
> i've noticed on kernel 2.6.35.y some weird screen blinking during
> e.g. <alt-tab> on kde4 with enabled accelerated desktop effects.
>
> i've started git bisect between good-v2.6.34 and bad-v2.6.35-rc1
> and after few steps git-bisect jumps to commit before v2.6.34.
>
> [~/src/linux/linux-2.6]$ make kernelrelease
> 2.6.34-rc6-00551-g7a6cb0d
>
> [~/src/linux/linux-2.6]$ git bisect log
> git bisect start
> # good: [e40152ee1e1c7a63f4777791863215e3faa37a86] Linus 2.6.34
> git bisect good e40152ee1e1c7a63f4777791863215e3faa37a86
> # bad: [67a3e12b05e055c0415c556a315a3d3eb637e29e] Linux 2.6.35-rc1
> git bisect bad 67a3e12b05e055c0415c556a315a3d3eb637e29e
> # good: [f8965467f366fd18f01feafb5db10512d7b4422c] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6
> git bisect good f8965467f366fd18f01feafb5db10512d7b4422c
> # bad: [d79df0b1eda0099a22cbcece01ce5e7d222450de] Merge git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6
> git bisect bad d79df0b1eda0099a22cbcece01ce5e7d222450de
> # good: [ac3ee84c604502240122c47b52f0542ec8774f15] Merge branch 'dbg-early-merge' of git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb
> git bisect good ac3ee84c604502240122c47b52f0542ec8774f15
>
> is it normal that bisect selects next step outside initial range?
It seems to me that it could happen - there are many merges of many
branches of the code - some of them may have really old commits.
>
> BR,
> Pawel.
>
> ps).
> please CC me on reply.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Slawa!
N.P.S.
next prev parent reply other threads:[~2010-09-27 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 18:51 Paweł Sikora
2010-09-27 19:26 ` N.P.S. N.P.S. [this message]
2010-09-27 20:29 ` Andreas Schwab
2010-09-27 21:51 ` Valdis.Kletnieks
2010-10-03 19:47 ` Paweł Sikora
2010-09-29 18:17 ` Paolo Ornati
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=AANLkTinCL--ndP3bbATGU46V8VJLs5hOWC++jbsodBiB@mail.gmail.com \
--to=napohybelskurwysynom2010@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pluto@agmk.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®