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

Re: What to do with patches that should go upstream?

From
Jeenu V <jeenuv@gmail.com>
Date
Jan 13, 2010, 10:34 UTC
Message-ID
<5195c8761001130234u59d7694bh699de788251f6764@mail.gmail.com>
In-Reply-To
<7vzl4inwh1.fsf@alter.siamese.dyndns.org>
On Wed, Jan 13, 2010 at 3:43 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 22 quoted lines
> Jeenu V <jeenuv@gmail.com> writes:
>
>> 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?
>
> I don't see B in your picture, so I may not be answering the question you
> wanted to ask, or you perhaps asked something other than the question you
> wanted to ask.  Having said that, I think you are asking two more-or-less
> independent questions.

Sorry, B was meant to be the branch at the bottom. But anyway I think I got hints on what I needed. Thank you for your descriptive reply.

-- 
:J
Previous: Junio C Hamano
Message 3 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.