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

Re: Preserve merge changes with rebase -p

From
MCMatteo Cypriani <mcy@lm7.fr>
Date
Jun 21, 2011, 15:07 UTC
Message-ID
<201106211707.53486.mcy@lm7.fr>
In-Reply-To
<4E00AE60.5000801@sohovfx.com>
Le mardi 21 juin 2011 16:44:48, Andrew Wong a écrit :
Show 6 quoted lines
> Unfortunately, I don't think there's any nice way to do it right now. I
> think what you could do for now is make the "pick <M>" into a "edit
> <M>", together with other changes you want to make. And then when you
> get to "edit M", do a "git cherry-pick -n -m 1 <M>", or "-m 2" depending
> on how your merge was done. That should bring your changes over. Then
> you just need resolve and add any conflicts, and do a "rebase --continue".
Thank you, I'll try that the next time.
> I imagine this is pretty useful feature to have too. I could look into
> adding this support when I got a chance.
That would be great, many thanks in advance!
Cheers,
  Matteo
-- 
Ma clef GPG est disponible sur keyserver.veridis.com
My GPG key is available on keyserver.veridis.com
Previous: Andrew Wong
Message 3 of 3 in “Preserve merge changes with rebase -p”
  1. Matteo CyprianiJun 21, 2011
  2. Andrew WongJun 21, 2011
  3. Matteo CyprianiJun 21, 2011

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.