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

How to add edges to visualize cherry-picks and ported patches

From
HGHartmut Goebel <h.goebel@crazy-compilers.com>
Date
Nov 24, 2018, 15:45 UTC
Message-ID
<9469d243-46c6-bf94-2586-84c59b866733@crazy-compilers.com>
Hi,

I hope this is the right place for this answer. If not, plaese point me to a more appropriate place.

A project  "P2" [2] forked from another project "P1" [1]  quite some time ago, both repos share a common history up to some point. After this point, P2 cherry-picked commits from P1, but did not merge P1 any longer. Unfortunately the author of P2 did not use any mechanism (e.g. an intermediate branch) to allow tracking up to which point P1 commits are considered. Thus the graph looks like this:

P1: --A--B--C--X--X--D--E--X--X--X--F--
P2: --Y--Y--A--B--C--D--E--Y--F--

I would like to add edges (say: another branch and merge-commits) to the graph to make it look something like this:

P1:      --A--B--C--X--X--D--E--X--X--X--F--
                  \           \           \
                   o-----------o-----------o---new branch
                  /           /           /
P2: --Y--Y--A--B--C-------D--E----Y------F--

Of course the new branch should contain the same code as the respective P2-commit. So at the end, the new branch couls become the P2's new "master" branch.

How can I achieve this (which commands to use)?
Is there some way to automate this? (e.g. based on `git cherry`)
Thanks in advance for any answer

[1] https://github.com/siacs/Conversations [2] https://github.com/kriztan/Pix-Art-Messenger

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |
Message 1 of 1 in “How to add edges to visualize cherry-picks and ported patches”
  1. Hartmut GoebelNov 24, 2018

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.