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

replacing a bad commit

From
BCBlu Corater <blu@daga.cl>
Date
Feb 5, 2007, 15:39 UTC
Message-ID
<20070205153949.GT14499@daga.cl>
Hello,

Here is the situation. Upstream realeses tarballs once in a while. I maintain local modifications. Every time upstream releases a tarball, I fast forward the 'upstream' branch, and merge into 'local' branch. My tree, currently, looks somewhat like this:

               o---o---o <--topic2
               |
               |  o---o---o <--topic1
               | /
   o---o---C---A---o---o <--local
  /   /   /  
 /   /   /
o---o---o---B <--upstream

Problem is, B should have been merged into 'local', at A, but I just realized it wasn't (probably due to my own stupidity).

I need to correct A, i.e. merge with B, but keeping the branches already in flux, and propagating the changes due to the merge to them. In short, replace A with a properly merged A'.

I tried branching from C and merging with B, then rebasing topic branches, but then I am not sure how to rebase 'local'to eliminate A.

Thanks in advance for any help.
-- 
Blu.
Next: Jakub Narebski
Message 1 of 8 in “replacing a bad commit”
  1. Blu CoraterFeb 5, 2007
  2. Jakub NarebskiFeb 5, 2007
  3. Blu CoraterFeb 5, 2007
  4. Shawn O. PearceFeb 5, 2007
  5. Blu CoraterFeb 5, 2007
  6. Jakub NarebskiFeb 5, 2007
  7. Blu CoraterFeb 5, 2007
  8. Shawn O. PearceFeb 5, 2007

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.