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

Re: git bisect; is there a way to pick only from the children of a given commit

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jul 1, 2009, 18:59 UTC
Message-ID
<alpine.DEB.1.00.0907012058290.4773@pacific.mpi-cbg.de>
In-Reply-To
<loom.20090701T170535-707@post.gmane.org>
Hi,
On Wed, 1 Jul 2009, Robert Stonehouse wrote:
> featureA (which was a new build target) was broken at HEAD. It had been 
> developed on the featureA branch. After featureA was merged into master, 
> featureB (which had branched from master at the same point as featureA) 
> was merged with master.

Why don't you just mark the merge commit that introduced featureA as bad, then?

Ciao, Dscho

Previous: Robert StonehouseNext: Sean Estabrooks
Message 2 of 6 in “git bisect; is there a way to pick only from the children of a given commit”
  1. Robert StonehouseJul 1, 2009
  2. Johannes SchindelinJul 1, 2009
  3. Sean EstabrooksJul 1, 2009
  4. Robert StonehouseJul 2, 2009
  5. Christian CouderJul 3, 2009
  6. Jakub NarebskiJul 1, 2009

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.