From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Andrew Morton <akpm@linux-foundation•org>,
Linus <torvalds@linux-foundation•org>
Subject: Re: linux-next: procedures
Date: Tue, 18 Nov 2008 08:47:57 -0800 [thread overview]
Message-ID: <20081118084757.5c92c878.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20081112173807.05cfadf0.sfr@canb.auug.org.au>
On Wed, 12 Nov 2008 17:38:07 +1100 Stephen Rothwell wrote:
...
> The following will cause a tree to be temporarily dropped from linux-next:
> - non-trivial conflicts with Linus' tree
> - build failures
Hi Stephen,
One clarification, please.
Does this mean build failures that _you_ see/experience during tree merging
and not other reported build failures?
Thanks,
~Randy
> - non-obvious conflicts with other trees (this will require
> us to come up with some way forward for the trees involved)
> - the contact for the tree being unresponsive
>
> Most conflicts will be notified to the contacts for the trees involved
> (some really trivial ones will not). Simple conflicts between trees I
> will try to fix up (if possible) and carry such resolutions as necessary.
>
> I will not, any more, carry fix up patches to make linux-next build or
> boot. If a tree is identified as causing such a problem, it will be
> dropped until the problem is fixed.
>
> This is all open to discussion ...
next prev parent reply other threads:[~2008-11-18 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 6:38 linux-next: procedures Stephen Rothwell
2008-11-18 16:47 ` Randy Dunlap [this message]
2008-11-18 20:24 ` 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=20081118084757.5c92c878.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=torvalds@linux-foundation$(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