Re: [PATCH] Create '--merges-only' option for 'git bisect'
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Apr 12, 2018, 11:35 UTC
- Message-ID
- <nycvar.QRO.7.76.6.1804121333340.65@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz>
- In-Reply-To
- <CAGZ79kbt=J5SHsHJTfOZYhgSdn9_gOjVBC3qp_oL0sC-b3ZRmw@mail.gmail.com>
Hi Stefan,
On Wed, 11 Apr 2018, Stefan Beller wrote:
Show 7 quoted lines
> On Wed, Apr 11, 2018 at 3:55 PM, Harald Nordgren > <haraldnordgren@gmail.com> wrote: > > When ran with '--merges-only', git bisect will only look at merge commits -- commits with 2 or more parents or the initial commit. > > There has been quite some talk on the mailing list, e.g. > https://public-inbox.org/git/20160427204551.GB4613@virgo.localdomain/ > which suggests a --first-parent mode instead.
I like that mode, but I would love to have *both*. And from what I see, it should be relatively easy to add the --first-parent mode on top of Harald's patches.
> For certain histories these are the same, but merges-only is more > restrictive for back-and-forth-cross merges.
You mean merges-only tests *more* in back-and-forth-cross-merges scenarios?
Ciao, Dscho