On Tue, Dec 26, 2017 at 05:54:21PM -0000, Philip Oakley wrote: > The key points were that bisect will search *all* heirarchy paths (unless > you tell it different). This means that all side heirarchies are also places > that bisect will search. > > Each time you give a 'good' history point it will trim the search history.
Is there a best practice about how to choose those history points? > IIRC you can also use the parsing options such as --first-parent to limit > the search history (so you find the point that the bad issue was merged in). Which git subcommand has this --first-parent option, and what would be my benefit of using it? > One thing to do is to use 'git describe' for the good tag/commit and the > commit found by the bisect and look at the implied history of the > ^I~J^K~L^M~N history flows, I guess that you will find that the bisected > commit is from such a side branch. You totally lost me here. Can you explain please? Greetings Marc, using git on a daily basis for years but still obviously well within the first third of the learning curve -- ----------------------------------------------------------------------------- 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 git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
