git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bisect limited to Merge Commits

From
Johannes Sixt <j6t@kdbg.org>
Date
Apr 27, 2016, 21:33 UTC
Message-ID
<57213041.5070506@kdbg.org>
In-Reply-To
<xmqq8tzy93ed.fsf@gitster.mtv.corp.google.com>
Am 27.04.2016 um 22:56 schrieb Junio C Hamano:
> So being able to stop at only commits on the first-parent chain is a
> valid and useful tool.  "git bisect --first-parent" is one of the
> things that are sometimes asked for.
With origin pointing to git.git, I attempted this:
  git bisect start
  git rev-list --first-parent --boundary origin..origin/pu |
    sed -ne s/-//p | xargs git bisect good
  git bisect bad origin/pu

and it starts bisecting among the 50-something first-parent commits between origin and origin/pu.

-- Hannes
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 6 in “Bisect limited to Merge Commits”
  1. Hagen Paul PfeiferApr 27, 2016
  2. Junio C HamanoApr 27, 2016
  3. Johannes SixtApr 27, 2016
  4. Junio C HamanoApr 27, 2016
  5. Hagen Paul PfeiferApr 28, 2016
  6. Jacob KellerApr 28, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.