{"thread":{"id":"47800","subject":"should \"git bisect skip\" not visually reduce number of revisions left?","startedAt":"2018-02-09T15:54:38Z","lastAt":"2018-02-09T15:54:38Z","messageCount":1,"participants":["Robert P. J. Day"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"338882","messageId":"alpine.LFD.2.21.1802091045380.25356@android-a172fe96dd584b41","threadId":"47800","inReplyTo":null,"subject":"should \"git bisect skip\" not visually reduce number of revisions left?","fromName":"Robert P. J. Day","fromEmail":"rpjday@crashcourse.ca","sentAt":"2018-02-09T15:54:31Z","receivedAt":"2018-02-09T15:54:38Z","isPatch":false,"sender":{"key":"rpjday@crashcourse.ca","avatar":"https://avatars.githubusercontent.com/u/226084077?v=4"},"body":"\n  perhaps i'm misreading something, but i'm trying to put together a\nhands-on example on how to use \"git bisect\" with feature branches as\nexplained here:\n\nhttps://blog.smart.ly/2015/02/03/git-bisect-debugging-with-feature-branches/\n\nand i'm using the linux kernel source as the content, so i started a\nbisection session with:\n\n$ git bisect start v4.15 v4.14\nBisecting: 8497 revisions left to test after this (roughly 13 steps)\n[5d352e69c60e54b5f04d6e337a1d2bf0dbf3d94a] Merge tag 'media/v4.15-1' of\nssh://gitolite.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media\n$\n\n  so far, apparently, so good. now i'm running the script:\n\n  for rev in $(git rev-list v4.14..v4.15 --merges --first-parent) ; do\n        echo \"=== ${rev} ===\"\n        git rev-list ${rev}^2 --not ${rev}^\n        git rev-list ${rev}^2 --not ${rev}^ | xargs git bisect skip\n  done\n\nso students can see the \"git bisect skip\" operations happening (there\nwill be 435 of them). first few lines of output verifying the opening\nskip operations:\n\n=== 24b1cccf922914f3d6eeb84036dde8338bc03abb ===\n1df37383a8aeabb9b418698f0bcdffea01f4b1b2\nBisecting: 8497 revisions left to test after this (roughly 13 steps)\n[5d352e69c60e54b5f04d6e337a1d2bf0dbf3d94a] Merge tag 'media/v4.15-1' of\nssh://gitolite.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media\n=== 32c6cdf75c9270848d2d0ed7c814eba05b47081f ===\ndd085168a74c99c3ebe7f813069e412eb8444243\n8a95b74d50825067fb6c8af7f9db03e711b1cb9d\n36b3a7726886f24c4209852a58e64435bde3af98\n5beda7d54eafece4c974cfa9fbb9f60fb18fd20a\n1d080f096fe33f031d26e19b3ef0146f66b8b0f1\n7e702d17ed138cf4ae7c00e8c00681ed464587c7\n40d4071ce2d20840d224b4a77b5dc6f752c9ab15\nBisecting: 8497 revisions left to test after this (roughly 13 steps)\n[5d352e69c60e54b5f04d6e337a1d2bf0dbf3d94a] Merge tag 'media/v4.15-1' of\nssh://gitolite.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media\n=== 07b0137c0268b8d0694a5f09284449353a1a6fed ===\n... and so on ...\n\n  what's weird(?) is that, while it's running right now, every \"git\nbisect skip\" operation doesn't change the apparent number of revisions\nleft to examine -- it's always:\n\n  Bisecting: 8497 revisions left to test after this (roughly 13 steps)\n\nis that not supposed to change to reflect the increasing number of\nrevisions to skip? or does that stay the same for the entire process\nuntil i start to bisect? or am i just doing something wrong?\n\nrday\n"}]}