From: "Paul E. McKenney" <paulmck@linux•vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis•org>
Cc: Fengguang Wu <fengguang.wu@intel•com>,
"ksummit-2012-discuss@lists•linux-foundation.org"
<ksummit-2012-discuss@lists•linux-foundation.org>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>
Subject: Re: [Ksummit-2012-discuss] [ATTEND] stable kernel stuff and grumpy maintainers [bisection/rebase/-next]
Date: Thu, 21 Jun 2012 17:03:20 -0700 [thread overview]
Message-ID: <20120622000320.GL2397@linux.vnet.ibm.com> (raw)
In-Reply-To: <1340322348.27036.218.camel@gandalf.stny.rr.com>
On Thu, Jun 21, 2012 at 07:45:48PM -0400, Steven Rostedt wrote:
> On Thu, 2012-06-21 at 16:38 -0700, Paul E. McKenney wrote:
>
> > Let me make sure that I understand the current state:
> >
> > 1. Fengguang pulls from my tree (presumably from rcu/next)
> > whenever I push something. He tests my commits in isolation
> > from other maintainers' commits.
> >
> > 2. Stephen also pulls from my tree (rcu/next) whenever I push
> > something. However, Stephen tests the merge of all
> > maintainers' commits.
> >
> > So it sounds to me that Stephen is already doing the job that Steven
> > is suggesting should be done.
> >
> > So, what am I missing here?
>
> That linux-next is only for code that's ready for the next release
> cycle.
>
> What would be nice is a single public repository that holds development
> code that is not ready for the next release cycle, but is in a "working
> state". Basically, one of your "not for inclusion" changes.
>
> For those of us with test machines, it may be nice that we also perform
> some testing, as Fengguang may not hit all permutations that others may
> find.
So you are suggesting:
3. Someone pulls from my tree (rcu/dev) whenever I push something,
and tests the merge of all maintainers' commits.
My rcu/dev branch is often just a preview of rcu/next, but I sometimes
have longer lived topic branches (for example, the current rcu/idle
branch with stuff related to Frederic's work). So maybe this tree
needs to pull from all of my "rcu/" branches.
Thanx, Paul
next prev parent reply other threads:[~2012-06-22 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1340126635.27036.34.camel@gandalf.stny.rr.com>
[not found] ` <4FE0B92D.8020108@windriver.com>
[not found] ` <1340128085.27036.46.camel@gandalf.stny.rr.com>
[not found] ` <4FE18DFB.5060807@parallels.com>
[not found] ` <3908561D78D1C84285E8C5FCA982C28F193223DB@ORSMSX104.amr.corp.intel.com>
[not found] ` <20120621034326.GA8601@localhost>
[not found] ` <1340280738.27036.130.camel@gandalf.stny.rr.com>
[not found] ` <4FE321C2.8010604@parallels.com>
[not found] ` <20120621133808.GA14716@localhost>
[not found] ` <1340287466.27036.161.camel@gandalf.stny.rr.com>
2012-06-21 15:26 ` [Ksummit-2012-discuss] [ATTEND] stable kernel stuff and grumpy maintainers [bisection/rebase/-next] Fengguang Wu
2012-06-21 15:51 ` Steven Rostedt
2012-06-21 23:38 ` Paul E. McKenney
2012-06-21 23:45 ` Steven Rostedt
2012-06-22 0:03 ` Paul E. McKenney [this message]
2012-06-22 0:29 ` Steven Rostedt
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=20120622000320.GL2397@linux.vnet.ibm.com \
--to=paulmck@linux$(echo .)vnet.ibm.com \
--cc=fengguang.wu@intel$(echo .)com \
--cc=ksummit-2012-discuss@lists$(echo .)linux-foundation.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rostedt@goodmis$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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