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

Detecting redundant commits

From
greened@obbligato.org <greened@obbligato.org>
Date
Jan 4, 2016, 15:59 UTC
Message-ID
<nngtwmtwd2q.fsf@lnx-dag.us.cray.com>

I am attempting to teach cherry-pick to handle redundant commits gracefully (via a new --skip-redundant-commits option) instead of aborting. However, I'm struggling a bit with how to check if the changes in a commit will become redundant when appied to the new HEAD.

I found diff_tree_sha1 which seems promising. Am I on the right track? If not, what's the best way to determine whether a commit object is redundant with respect to HEAD?

                           -David
Next: Jeff King
Message 1 of 4 in “Detecting redundant commits”
  1. greened@obbligato.orgJan 4, 2016
  2. Jeff KingJan 5, 2016
  3. David GreeneJan 5, 2016
  4. David A. GreeneJan 8, 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.