From: Stefan Richter <stefanr@s5r6•in-berlin.de>
To: Greg KH <greg@kroah•com>
Cc: Geert Uytterhoeven <geert@linux-m68k•org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: Can you add the staging tree to -next?
Date: Tue, 18 Nov 2008 19:36:42 +0100 [thread overview]
Message-ID: <49230B3A.2000509@s5r6.in-berlin.de> (raw)
In-Reply-To: <20081114173258.GC22980@kroah.com>
Greg KH wrote on November 14:
> On Fri, Nov 14, 2008 at 08:42:48AM +0100, Geert Uytterhoeven wrote:
>> Apart from the patches you receive against -next, is there any other
>> advantage, giving staging is disabled?
>
> That is a huge advantage, don't discount it. My staging tree has over
> 150 patches in it right now, and is quite diverged from what is in
> Linus's tree. I have been getting the same patches sent over and over
> to fix the same thing that is already resolved in my tree, as the
> developers are working against -next thinking that they were working
> with the latest development tree.
These people are missing that -next is not a development tree.
(Unless final integration tests count still as development.)
--
Stefan Richter
-=====-==--- =-== =--=-
http://arcgraph.de/sr/
prev parent reply other threads:[~2008-11-18 18:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 23:56 Can you add the staging tree to -next? Greg KH
2008-11-13 23:44 ` Stephen Rothwell
2008-11-14 0:01 ` Greg KH
2008-11-14 0:13 ` J.R. Mauro
2008-11-14 0:22 ` Greg KH
2008-11-14 0:25 ` J.R. Mauro
2008-11-14 7:42 ` Geert Uytterhoeven
2008-11-14 7:50 ` Stephen Rothwell
2008-11-14 14:16 ` Geert Uytterhoeven
2008-11-14 17:32 ` Greg KH
2008-11-14 22:28 ` J.R. Mauro
2008-11-14 23:06 ` Greg KH
2008-11-14 23:43 ` J.R. Mauro
2008-11-18 18:36 ` Stefan Richter [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=49230B3A.2000509@s5r6.in-berlin.de \
--to=stefanr@s5r6$(echo .)in-berlin.de \
--cc=geert@linux-m68k$(echo .)org \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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