Re: Git bisect does not find commit introducing the bug
- From
- Alex Hoffman <spec@gal.ro>
- Date
- Feb 21, 2017, 19:40 UTC
- Message-ID
- <CAMX8fZUR4h0T3hBmh6Z_0=f5LHFJetOi-vO_JJgnYPB7KjU_bg@mail.gmail.com>
- In-Reply-To
- <4C20E99781EC4D6D82D48FBF9D9472A1@PhilipOakley>
> isn't that spelt `--ancestry-path` ? > (--ancestry-path has it's own issues such as needing an --first-parent-show > option, but that's possibly a by the by)
Indeed it is spelled `--ancestry-path`. And interestingly enough you may use it multiple times with the wanted effect in our case (e.g when the user has multiple good commit and a single bad commit before running the bisect itself). Also it is `--first-parent` (not `--first-parent-show`), but I do not understand why do we need this option? What kind of issues does `--ancestry-path` have?
Best regards, VG