{"thread":{"id":"21050","subject":"is smarter bisect possible?","startedAt":"2009-09-25T07:59:33Z","lastAt":"2009-09-25T09:37:06Z","messageCount":2,"participants":["Arkadiusz Miśkiewicz","Johannes Sixt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"123758","messageId":"4ABC7865.7010705@viscovery.net","threadId":"21050","inReplyTo":"h9hrv3$cao$1@ger.gmane.org","subject":"Re: is smarter bisect possible?","fromName":"Johannes Sixt","fromEmail":"j.sixt@viscovery.net","sentAt":"2009-09-25T07:59:33Z","receivedAt":"2009-09-25T07:59:33Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Arkadiusz Miśkiewicz schrieb:\n> I have such problem. Linus kernel tree merged some feature \n> (94e0fb086fc5663c38bbc0fe86d698be8314f82f) that was developed in .31rc9 era.\n> \n> Current Linus kernel tree with that feature merged shows some regression. \n> Tree just before that merge doesn't show regression.\n> \n> Now if I start to bisect just that feature (good \n> b7f21bb2e23b4fec16b448a34889f467465be659, bad \n> 94e0fb086fc5663c38bbc0fe86d698be8314f82f) then git gets me whole tree back \n> to .31rc9 era which... doesn't show any problems.\n> \n> This means that only combined current Linus tree and that feature shows a \n> problem.\n\nTry this:\n\nhttp://www.kernel.org/pub/software/scm/git/docs/user-manual.html#bisect-merges\n\n-- Hannes\n"},{"id":"123757","messageId":"h9hrv3$cao$1@ger.gmane.org","threadId":"21050","inReplyTo":null,"subject":"is smarter bisect possible?","fromName":"Arkadiusz Miśkiewicz","fromEmail":"arekm@maven.pl","sentAt":"2009-09-25T09:37:06Z","receivedAt":"2009-09-25T09:37:06Z","isPatch":false,"sender":{"key":"arekm@maven.pl","avatar":null},"body":"\nHi,\n\nI have such problem. Linus kernel tree merged some feature \n(94e0fb086fc5663c38bbc0fe86d698be8314f82f) that was developed in .31rc9 era.\n\nCurrent Linus kernel tree with that feature merged shows some regression. \nTree just before that merge doesn't show regression.\n\nNow if I start to bisect just that feature (good \nb7f21bb2e23b4fec16b448a34889f467465be659, bad \n94e0fb086fc5663c38bbc0fe86d698be8314f82f) then git gets me whole tree back \nto .31rc9 era which... doesn't show any problems.\n\nThis means that only combined current Linus tree and that feature shows a \nproblem.\n\nIs it possible to make git bisect test current tree + parts of that merge \ninstead going back to .31rc9 era with the whole tree?\n\n-- \nArkadiusz Miśkiewicz        PLD/Linux Team\narekm / maven.pl            http://ftp.pld-linux.org/\n"}]}