Re: is smarter bisect possible?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Arkadiusz Miśkiewicz schrieb:
> I have such problem. Linus kernel tree merged some feature 
> (94e0fb086fc5663c38bbc0fe86d698be8314f82f) that was developed in .31rc9 era.
> 
> Current Linus kernel tree with that feature merged shows some regression. 
> Tree just before that merge doesn't show regression.
> 
> Now if I start to bisect just that feature (good 
> b7f21bb2e23b4fec16b448a34889f467465be659, bad 
> 94e0fb086fc5663c38bbc0fe86d698be8314f82f) then git gets me whole tree back 
> to .31rc9 era which... doesn't show any problems.
> 
> This means that only combined current Linus tree and that feature shows a 
> problem.

Try this:

http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#bisect-merges

-- Hannes

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]