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

Patching bad commits

From
Michael Witten <mfwitten@gmail.com>
Date
Jun 28, 2010, 22:03 UTC
Message-ID
<4c291e41.4f1ee30a.3484.fffff729@mx.google.com>

Sometimes bisecting is less than useful because a number of commits fail to build.

How about implementing something SIMILAR to "git notes" (perhaps even using "git notes") to store and apply patches for such bad commits?

For instance, bisecting could transparently apply any patches that are necessary to make a bad commit actually buildable; such patches could be distributed as usual for the benefit of others.

I'm thinking that a "patch note" could have 2 forms:
    * A plain patch file (or maybe a git tree of patches).
    * A reference to another commit that should be checked
      out instead.
Is this a worthwhile idea?

Sincerely, Michael Witten

Next: Avery Pennarun
Message 1 of 4 in “Patching bad commits”
  1. Michael WittenJun 28, 2010
  2. Avery PennarunJun 28, 2010
  3. Antriksh PanyJul 5, 2010
  4. Sverre RabbelierJun 28, 2010

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.