git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeenu V <jeenuv@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What to do with patches that should go upstream?
Date: Wed, 13 Jan 2010 16:04:33 +0530	[thread overview]
Message-ID: <5195c8761001130234u59d7694bh699de788251f6764@mail.gmail.com> (raw)
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:
> 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

      reply	other threads:[~2010-01-13 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13  9:51 What to do with patches that should go upstream? Jeenu V
2010-01-13 10:13 ` Junio C Hamano
2010-01-13 10:34   ` Jeenu V [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5195c8761001130234u59d7694bh699de788251f6764@mail.gmail.com \
    --to=jeenuv@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).