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

git merge after git cherry-pick?

From
PLPeter Valdemar Mørch (Lists) <4ux6as402@sneakemail.com>
Date
Jul 23, 2008, 17:14 UTC
Message-ID
<48876709.3090504@sneakemail.com>
Hi,
Still being a newbie...

On a branch, b, made off of master, I've made the commits b1, b2, b3 and b4.

Back on master, I need commit b1 and b3 immediately. So I:

$ git checkout master $ git cherry-pick "b1's SHA" $ git cherry-pick "b3's SHA"

Now, both b and master contain b1 and b3. How do I now create a log of "what remains to be merged from b to master", i.e. only b2 and b4? And how do I merge b2 and b4 to master, so master's log shows b1, b3, b2 and b4 and doesn't show b1 and b3 twice, which is what I get if I:

$ git merge b

after the cherry-picks above. Also I noticed, that if I merge master into b (to keep up-to-date with master) b1 and b3 are also mentioned twice.

I did notice that cherry-pick created new SHA1 IDs for the commits for b1 and b3 on master (as indeed man cherry-pick also says). Maybe cherry-pick is not the right tool for the job. Is there another way to "copy"/"merge" only b1 and b3 (but not b2 and b4) from b into master maintaining merge history and avoiding them being mentioned twice later?

At the time of writing b1-b4, I did not know that b1 and b3 would be needed separately, so I didn't put (b1 and b3) and (b2 and b4) on separate branches. I did notice though, that they weren't an intricate part of "the new feature". Is it required that I then do the work in separate branches?

I hope this is possible as I'm thrilled with git!
Peter
-- 
Peter Valdemar Mørch
http://www.morch.com
Next: SZEDER Gábor
Message 1 of 4 in “git merge after git cherry-pick?”
  1. Peter Valdemar Mørch (Lists)Jul 23, 2008
  2. SZEDER GáborJul 23, 2008
  3. Peter Valdemar Mørch (Lists)Jul 23, 2008
  4. Jakub NarebskiJul 23, 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.