{"thread":{"id":"17939","subject":"Is this a git-bisect bug?","startedAt":"2009-02-21T17:07:28Z","lastAt":"2009-02-22T06:47:29Z","messageCount":4,"participants":["walt","Teemu Likonen","Christian Couder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"105728","messageId":"gnpccl$l69$1@ger.gmane.org","threadId":"17939","inReplyTo":null,"subject":"Is this a git-bisect bug?","fromName":"walt","fromEmail":"w41ter@gmail.com","sentAt":"2009-02-21T17:07:28Z","receivedAt":"2009-02-21T17:07:28Z","isPatch":false,"sender":{"key":"w41ter@gmail.com","avatar":null},"body":"I'm using the current git.git to bisect a bug in Linus.git.\n\nI got this far and then ran into trouble:\ngood 2.6.29-rc5-00094-gc951aa6\nbad  2.6.29-rc5-00112-g3501033\n\nA glance at git log will show that those two commits were\nboth from Feb 17 with only one other commit between them.\n\nSo, why does this happen?:\n\n$git bisect start 3501033 c951aa6\nBisecting: 8 revisions left to test after this\nbe716615fe596ee117292dc615e95f707fb67fd1] x86, vm86: fix preemption bug\n\ngit log shows that commit is from Jan 13, way back in 2.6.29-rc3.\nCan anyone reproduce/explain this?\n\nThanks!\n"},{"id":"105731","messageId":"87skm7em72.fsf@iki.fi","threadId":"17939","inReplyTo":"gnpccl$l69$1@ger.gmane.org","subject":"Re: Is this a git-bisect bug?","fromName":"Teemu Likonen","fromEmail":"tlikonen@iki.fi","sentAt":"2009-02-21T17:25:53Z","receivedAt":"2009-02-21T17:25:53Z","isPatch":false,"sender":{"key":"tlikonen@iki.fi","avatar":null},"body":"On 2009-02-21 09:07 (-0800), walt wrote:\n\n> I'm using the current git.git to bisect a bug in Linus.git.\n>\n> I got this far and then ran into trouble:\n> good 2.6.29-rc5-00094-gc951aa6\n> bad  2.6.29-rc5-00112-g3501033\n>\n> A glance at git log will show that those two commits were\n> both from Feb 17 with only one other commit between them.\n>\n> So, why does this happen?:\n>\n> $git bisect start 3501033 c951aa6\n> Bisecting: 8 revisions left to test after this\n> be716615fe596ee117292dc615e95f707fb67fd1] x86, vm86: fix preemption bug\n\nSomeone will probably give real explanation but non-linear development\nis part of it:\n\n$ git log --graph --pretty=oneline --abbrev-commit c951aa6..3501033\n\n*   3501033 Merge branch 'x86-fixes-for-linus' of git:// [...]\n|\\  \n| * be71661 x86, vm86: fix preemption bug\n| * e49590b x86, olpc: fix model detection without OFW\n| * b13e246 x86, hpet: fix for LS21 + HPET = boot hang\n| * 7ad9de6 x86: CPA avoid repeated lazy mmu flush\n| * 34b0900 x86: warn if arch_flush_lazy_mmu_cpu is called in [...]\n| * d85cf93 x86/paravirt: make arch_flush_lazy_mmu/cpu disable [...]\n| * be03d9e x86, pat: fix warn_on_once() while mapping 0-1MB range [...]\n| * 4f06b04 x86/cpa: make sure cpa is safe to call in lazy mmu mode\n| * 9f339e7 x86, ptrace, mm: fix double-free on race\n*   8ce9a75 Merge branch 'core-fixes-for-linus' of git:// [...]\n|\\  \n| * 9af8814 iommu: fix Intel IOMMU write-buffer flushing\n| * 2fff78c futex: fix reference leak\n* b30b774 Merge branch 'merge' of git://git.kernel.org/pub/scm/ [...]\n* 26456dc powerpc/vsx: Fix VSX alignment handler for regs 32-63\n* 0047656 powerpc/ps3: Move ps3_mm_add_memory to device_initcall\n* 06eccea powerpc/mm: Fix numa reserve bootmem page selection\n* fbc78b0 powerpc/mm: Fix _PAGE_CHG_MASK to protect _PAGE_SPECIAL\n"},{"id":"105744","messageId":"gnppph$r8r$1@ger.gmane.org","threadId":"17939","inReplyTo":"87skm7em72.fsf@iki.fi","subject":"Re: Is this a git-bisect bug?","fromName":"walt","fromEmail":"w41ter@gmail.com","sentAt":"2009-02-21T20:56:20Z","receivedAt":"2009-02-21T20:56:20Z","isPatch":false,"sender":{"key":"w41ter@gmail.com","avatar":null},"body":"Teemu Likonen wrote:\n> On 2009-02-21 09:07 (-0800), walt wrote:\n>\n>> I'm using the current git.git to bisect a bug in Linus.git.\n>>\n>> I got this far and then ran into trouble:\n>> good 2.6.29-rc5-00094-gc951aa6\n>> bad  2.6.29-rc5-00112-g3501033\n>>\n>> A glance at git log will show that those two commits were\n>> both from Feb 17 with only one other commit between them.\n>>\n>> So, why does this happen?:\n>>\n>> $git bisect start 3501033 c951aa6\n>> Bisecting: 8 revisions left to test after this\n>> be716615fe596ee117292dc615e95f707fb67fd1] x86, vm86: fix preemption bug\n>\n> Someone will probably give real explanation but non-linear development\n> is part of it:\n>\n> $ git log --graph --pretty=oneline --abbrev-commit c951aa6..3501033\n>\n> *   3501033 Merge branch 'x86-fixes-for-linus' of git:// [...]\n> |\\\n> | * be71661 x86, vm86: fix preemption bug\n > ...\n\nI see now that git bisect actually found the guilty commit for me,\nbut completely confused me by turning out five kernels in a row\nwith the names 2.6.29-rc3-00nnn while I was bisecting an rc5 kernel.\nI stopped because of those tag names when I should have just forged\nahead.\n\nI would be interested to hear opinions on whether that rc3 tag is\nthe correct one to use for the bisected kernels.\n\nThanks.\n"},{"id":"105755","messageId":"200902220747.29932.chriscool@tuxfamily.org","threadId":"17939","inReplyTo":"gnppph$r8r$1@ger.gmane.org","subject":"Re: Is this a git-bisect bug?","fromName":"Christian Couder","fromEmail":"chriscool@tuxfamily.org","sentAt":"2009-02-22T06:47:29Z","receivedAt":"2009-02-22T06:47:29Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Le samedi 21 février 2009, walt a écrit :\n> Teemu Likonen wrote:\n> > On 2009-02-21 09:07 (-0800), walt wrote:\n> >> I'm using the current git.git to bisect a bug in Linus.git.\n> >>\n> >> I got this far and then ran into trouble:\n> >> good 2.6.29-rc5-00094-gc951aa6\n> >> bad  2.6.29-rc5-00112-g3501033\n> >>\n> >> A glance at git log will show that those two commits were\n> >> both from Feb 17 with only one other commit between them.\n> >>\n> >> So, why does this happen?:\n> >>\n> >> $git bisect start 3501033 c951aa6\n> >> Bisecting: 8 revisions left to test after this\n> >> be716615fe596ee117292dc615e95f707fb67fd1] x86, vm86: fix preemption\n> >> bug\n> >\n> > Someone will probably give real explanation but non-linear development\n> > is part of it:\n> >\n> > $ git log --graph --pretty=oneline --abbrev-commit c951aa6..3501033\n> >\n> > *   3501033 Merge branch 'x86-fixes-for-linus' of git:// [...]\n> >\n> > |\\\n> > | * be71661 x86, vm86: fix preemption bug\n>  >\n>  > ...\n>\n> I see now that git bisect actually found the guilty commit for me,\n> but completely confused me by turning out five kernels in a row\n> with the names 2.6.29-rc3-00nnn while I was bisecting an rc5 kernel.\n> I stopped because of those tag names when I should have just forged\n> ahead.\n>\n> I would be interested to hear opinions on whether that rc3 tag is\n> the correct one to use for the bisected kernels.\n\nPlease have a look at this:\n\nhttp://thread.gmane.org/gmane.comp.version-control.git/99967/focus=99977\n\nRegards,\nChristian.\n"}]}