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

marking (cherry-pick) commits ?

From
MWMarc Weber <marco-oweber@gmx.de>
Date
Mar 6, 2009, 14:41 UTC
Message-ID
<20090306144125.GA14569@gmx.de>
I've this situation:
base --------- branch_A (svn trunk)
  ` ---------- branch_B (svn branch )

Some cherry picks have been done both dirctions. Is there a way show gitk branch_A branch_B and mark cherry-picks? I only know about --left-right --cherry-pick and such omitting them.

How does --cherry-pick work? Is it based on git-commit-id? Probably it would be enough to write a simple script iterating over both brnaches adding some temporary tags pointing out the pairs of cherry-picked patches..

Is there another way "marking" patches? Maybe it would be fun to use

git tab tmp_dont_commit_red_message git tab tmp_dont_commit_green_message

and ask gitk to show them in red and green?

Can I tell git push to not push all tags starting with tmp_dont_commit_ ?

There are only about 120 patches.. So I can manually handle that case.. But I guess git can do better.

Sincerly Marc Weber

Message 1 of 1 in “marking (cherry-pick) commits ?”
  1. Marc WeberMar 6, 2009

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.