linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: linux-next <linux-next@vger.kernel.org>
Subject: Re: Multiple for-next branches from same tree
Date: Thu, 7 Mar 2013 22:24:46 +1100	[thread overview]
Message-ID: <20130307222446.d2b14a7a3785ef99dbf098b8@canb.auug.org.au> (raw)
In-Reply-To: <51382DCA.5010209@synopsys.com>

[-- Attachment #1: Type: text/plain, Size: 745 bytes --]

Hi Vineet,

On Thu, 7 Mar 2013 11:33:54 +0530 Vineet Gupta <Vineet.Gupta1@synopsys.com> wrote:
>
> With ARC arch merged in 3.9-rc1 I feel the need for a revised workflow.
> 
> I intend to have 2 branches for -next exposure: for-curr and for-next.
> * for-curr would contain the bug fixes for this release to be sent to Linus at
> some point in time.
> * for-next obviously is next release stuff and will be rebased off for-curr.

I have several sets of branches like that and it works fine.

Occasionally, the branches will conflict, but that can be sorted by
merging the for-curr branch into the for-next branch after Linus has
merged the for-curr branch.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-03-07 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07  6:03 Multiple for-next branches from same tree Vineet Gupta
2013-03-07 11:24 ` Stephen Rothwell [this message]
2013-03-07 12:25   ` Vineet Gupta
2013-03-07 13:46     ` Stephen Rothwell

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=20130307222446.d2b14a7a3785ef99dbf098b8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=linux-next@vger.kernel.org \
    /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).