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

Re: help doing a hotfix bisect: cherry-pick -m ??

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 7, 2012, 19:27 UTC
Message-ID
<7v627py6or.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAJfuBxwBn-WFw+nci1MpdWQvyXkrhyB3maXPwMAsxggTE3gz3Q@mail.gmail.com>
Jim Cromie <jim.cromie@gmail.com> writes:
> Broader question:
> Im thinking that having a hotfix branch, and merging --no-commit would
> work better,
> especially when bisection lands on a commit which already contains
> some of those in the hotfix branch.

When your history leading to the "bad" commit contains only part of the hot-fix branch and not all of it, that may work better.

Previous: Jim CromieNext: Jim Cromie
Message 2 of 3 in “help doing a hotfix bisect: cherry-pick -m ??”
  1. Jim CromieSep 7, 2012
  2. Junio C HamanoSep 7, 2012
  3. Jim CromieSep 7, 2012

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.