On Mon, Dec 25, 2017 at 11:21:36PM -0000, Philip Oakley wrote: > Possibly include more good commits in the list. I suspect that there are > multiple branches that merge into master between those two tags, and that > some of those brancfes have fork points from before the given good tag, so > git has to search down all of those other side branches, and found one. > Hence the report of an rc branch as the first bad commit.
Assuming that it would probably not help including commits that were marked as good in the first bisect, How would I choose such commits? Unfortunately, it takes multiple days to be reasonably (but not even then absolutely) sure that a commit is "good". It is significantly more easy to identify a "bad" commit with this issue. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421 -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
