{"thread":{"id":"46503","subject":"git bisect \"commits left\" miscount","startedAt":"2017-08-02T15:56:12Z","lastAt":"2017-08-02T15:56:12Z","messageCount":1,"participants":["Ben Boeckel"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"325435","messageId":"20170802155605.GA31021@megas.kitware.com","threadId":"46503","inReplyTo":null,"subject":"git bisect \"commits left\" miscount","fromName":"Ben Boeckel","fromEmail":"mathstuf@gmail.com","sentAt":"2017-08-02T15:56:05Z","receivedAt":"2017-08-02T15:56:12Z","isPatch":false,"sender":{"key":"mathstuf@gmail.com","avatar":"https://avatars.githubusercontent.com/u/97253?v=4"},"body":"Hi,\n\nWhen bisecting given a set of paths, git counts the number of remaining\ncommits improperly. Here's example output (based in the git.git\nrepository):\n\n    % git bisect start -- sha1_file.c\n    % git bisect good v2.10.0\n    % git bisect bad v2.10.3\n    Bisecting: 1 revision left to test after this (roughly 1 step)\n    [f7f0a87e0a27a1baaf782af7cec18fd23fdf35de] Merge branch 'jc/verify-loose-object-header' into maint\n    % git bisect good\n    Bisecting: 0 revisions left to test after this (roughly 0 steps)\n    [5827a03545663f6d6b491a35edb313900608568b] fetch: use \"quick\" has_sha1_file for tag following\n    % git bisect good\n    Bisecting: -1 revisions left to test after this (roughly 0 steps)\n    [39000e849970a554a257577dcb2fb844a523a1d1] Merge branch 'jk/fetch-quick-tag-following' into maint\n    % git bisect good\n    No testable commit found.\n    Maybe you started with bad path parameters?\n\nNote that it ends up with -1 revisions left and it doesn't end up with a\n\"this commit is the first bad commit\" message.\n\nShould git find the newest ancestors(s) of the given bad commit which\nmodifies the given paths and start counting from there?\n\nI haven't bisected to find out when this was introduced yet (first seen\nwith 2.9.4; confirmed with 2.14.0-rc1).\n\nThanks,\n\n--Ben\n"}]}