From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next <linux-next@vger.kernel.org>
Subject: Multiple for-next branches from same tree
Date: Thu, 7 Mar 2013 11:33:54 +0530 [thread overview]
Message-ID: <51382DCA.5010209@synopsys.com> (raw)
Hi Stephen,
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.
The other strategy, personally less preferred, is to keep only for-next and tag it
at right cut off point when sending pull request to Linus. Do you see any
semantical differences in the two approaches.
One (hypothetical) scenario that comes to my mind is that if for-curr introduces a
conflict, which for-next fixes up somehow, that would still be caught in both the
cases.
Comments !
Thx,
-Vineet
next reply other threads:[~2013-03-07 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 6:03 Vineet Gupta [this message]
2013-03-07 11:24 ` Multiple for-next branches from same tree Stephen Rothwell
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=51382DCA.5010209@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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