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

What to do with patches that should go upstream?

From
Jeenu V <jeenuv@gmail.com>
Date
Jan 13, 2010, 09:51 UTC
Message-ID
<5195c8761001130151q12ac636cnc69513087320195@mail.gmail.com>
Hi,

I'd like to know what's the best practice to follow when one discovers that a change that's been applied on the current branch, has to actually go upstream. For example, in the following figure,

     A
-O---O-+
        \        A'  B'
-O---O---O---O---O---O---O W
            /
  -O----O--+

W is the current working branch. But there are commits A' and B' which should go upstream. What I wanted to know is the next step from here.

1) Do I switch to A and B, and then cherry pick the commits A' and B'?
2) If I send the patch out to include in upstream, wouldn't it
conflict the next time I happen to merge from A or B?
Please suggest.
-- 
:J
Next: Junio C Hamano
Message 1 of 3 in “What to do with patches that should go upstream?”
  1. Jeenu VJan 13, 2010
  2. Junio C HamanoJan 13, 2010
  3. Jeenu VJan 13, 2010

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.