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

duplicate commits after git rebase -i HEAD~10

From
Mathieu Malaterre <mathieu.malaterre@gmail.com>
Date
Dec 3, 2010, 15:04 UTC
Message-ID
<AANLkTi=W9MyCuOuk49AtCxR7nTa5xkddY_2HkhOvQip-@mail.gmail.com>
Hi,
  I am trying to understand what I did wrong in my git rebase and
eventually I would like to repair my mistakes. Basically after a git
rebase, I ended up with duplicate *identical* commits. One was on the
master branch and one was on a local branch which was merge to master.
$ git log --graph
...
| * commit 662be6a57a6a64840ba0f1b29d422ab6b129ff04
| | Author:
| | Date:   Fri Dec 3 15:27:10 2010 +0100
| |
| |     BUG: 122 Work toward a better framework for Java wrapping testing
| |
* | commit 1f639b9fd6c04eb48a69d84749bb30d7dd816382
| | Author:
| | Date:   Fri Dec 3 15:42:16 2010 +0100
| |
| |     BUG: 122 Work toward a better framework for Java wrapping testing
| |
Is there a way to properly merge identical commit back together ?
Thanks !
-- 
Mathieu
Next: Jeff King
Message 1 of 3 in “duplicate commits after git rebase -i HEAD~10”
  1. Mathieu MalaterreDec 3, 2010
  2. Jeff KingDec 3, 2010
  3. Gavin GuoDec 14, 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.