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

stgit - continue rebase after merge conflict?

From
ACAlex Chiang <achiang@hp.com>
Date
Feb 26, 2008, 14:57 UTC
Message-ID
<20080226145725.GA24987@ldl.fc.hp.com>
Hi Catalin,
How does one do a stg rebase if there are merge conflicts?
I see:
-------------------------------------------------------
achiang@blender:~/kernels/linux-2.6$ stg rebase origin
Upgraded branch stg-pci-slots to format version 2
Checking for changes in the working directory ... done
Popping all applied patches ... done
Rebasing to "origin" ... done
Pushing patch "0001-Remove-path-attribute-from-sgi_hotplug.patch" ... done
Pushing patch "0002-Construct-one-fakephp-slot-per-pci-slot.patch" ... 
  CONFLICT (content): Merge conflict in drivers/pci/hotplug/fakephp.c
  Error: The merge failed during "push".
         Revert the operation with "push --undo".
  stg rebase: 1 conflict(s)
-------------------------------------------------------

This output tells you how to undo the rebase, but doesn't give any clues on how to continue it, like git would:

------------------------------------------------------- When you have resolved this problem run "git rebase --continue". If you would prefer to skip this patch, instead run "git rebase --skip". To restore the original branch and stop rebasing run "git rebase --abort". -------------------------------------------------------

Doing an 'stg help rebase' isn't so helpful.
My *guess* is that I want to:
	- manually resolve the merge conflicts
	- stg refresh
	- ???
Any hints are appreciated.
Thanks.
/ac
Next: Catalin Marinas
Message 1 of 7 in “stgit - continue rebase after merge conflict?”
  1. Alex ChiangFeb 26, 2008
  2. Catalin MarinasFeb 26, 2008
  3. Alex ChiangFeb 26, 2008
  4. Karl HasselströmFeb 27, 2008
  5. Alex ChiangFeb 28, 2008
  6. Catalin MarinasFeb 28, 2008
  7. Karl HasselströmFeb 29, 2008

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.