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

git-rerere vs rebase --skip

From
Mike Hommey <mh@glandium.org>
Date
Aug 28, 2012, 21:52 UTC
Message-ID
<20120828215202.GB7702@glandium.org>
Hi,

In one of my workflows, I constantly rebase topic branches on top of new upstream imports. As there are several upstream import branches, I have similar topic branches on top of different imports. When rebasing the topic branches, I can hit conflict resolution that I already had to do for other topic branches on another upstream import branch. Here, git rerere is very helpful. But sometimes, the conflict resolution is just to skip the patch, because it was incorporated upstream in a way that git doesn't detect, or it was obsoleted, or whatever. In such cases, git rerere is not being helpful because it doesn't store any information about that, and I have to check again if that's an actual conflict to solve or a patch to skip again.

It would be helpful if there was a rebase --skip mode that would tell rerere to record that the resolution *is* --skip.

Mike
Next: Junio C Hamano
Message 1 of 2 in “git-rerere vs rebase --skip”
  1. Mike HommeyAug 28, 2012
  2. Junio C HamanoAug 28, 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.