{"thread":{"id":"39482","subject":"GIT BISECT old/new (fix/unfixed)","startedAt":"2015-06-01T14:24:18Z","lastAt":"2015-06-01T14:24:18Z","messageCount":1,"participants":["Antoine Delaite"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"262596","messageId":"1363968792.246885.1433168658027.JavaMail.zimbra@ensimag.grenoble-inp.fr","threadId":"39482","inReplyTo":"1762682958.245864.1433168080478.JavaMail.zimbra@ensimag.grenoble-inp.fr","subject":"GIT BISECT old/new (fix/unfixed)","fromName":"Antoine Delaite","fromEmail":"antoine.delaite@ensimag.grenoble-inp.fr","sentAt":"2015-06-01T14:24:18Z","receivedAt":"2015-06-01T14:24:18Z","isPatch":false,"sender":{"key":"antoine.delaite@ensimag.grenoble-inp.fr","avatar":"https://avatars.githubusercontent.com/u/12510393?v=4"},"body":"Hi,\n\ngit bisect old/new is an alternative to good/bad, which can be confusing to use \nin some situations. \n\nA work on it was done a few years ago, it is partially working but there are a \nlot of issues. \n\nWe based on Christian Couder's github: \nhttps://github.com/chriscool/git/commits/boldnew2 \n\nWe're currently working on it again. Older discussions lead to this state: \n\n>Some commands are still not available for old/new: \n> \n> * git bisect start [<new> [<old>...]] is not possible: the commits \n> will be treated as bad and good. \n> * git rev-list --bisect does not treat the revs/bisect/new and \n> revs/bisect/old-SHA1 files. \n> * thus, git bisect run <cmd> is not available for new/old. \n> * git bisect visualize seem to work partially: the tags are displayed \n> correctly but the tree is not limited to the bisect section. \n\nWe did some testing with git bisect old/new and found that it was quite \nworking, returning the commit that introduces the fix. \n\nWe noticed an other error once the bisection is finished : \nfatal: 'refs/bisect/bad' - not a valid ref \n\nWe did not understand why git bisect run is supposed not to work with old/new. \nThe only thing is that the script has to return 0 if the version is old, which \nseems to work like in good/bad mode. This should be modified if the user wants \nto use the same script to find a fix or a regression (without changing the \nreturn value each time). \n\nAntoine D \n"}]}