From: Nicolas Kaiser <nikai@nikai.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH] docs: update the development process document
Date: Fri, 25 Mar 2011 20:36:07 +0100 [thread overview]
Message-ID: <20110325203607.05061aa2@absol.kitzblitz> (raw)
In-Reply-To: <20110325123031.45b6a217@bike.lwn.net>
* Jonathan Corbet <corbet@lwn.net>:
> @@ -287,25 +293,14 @@ Some information about linux-next has been gathered at:
>
> http://linux.f-seidel.de/linux-next/pmwiki/
>
> -How the linux-next tree will fit into the development process is still
> -changing. As of this writing, the first full development cycle involving
> -linux-next (2.6.26) is coming to an end; thus far, it has proved to be a
> -valuable resource for finding and fixing integration problems before the
> -beginning of the merge window. See http://lwn.net/Articles/287155/ for
> -more information on how linux-next has worked to set up the 2.6.27 merge
> -window.
> -
> -Some developers have begun to suggest that linux-next should be used as the
> -target for future development as well. The linux-next tree does tend to be
> -far ahead of the mainline and is more representative of the tree into which
> -any new work will be merged. The downside to this idea is that the
> -volatility of linux-next tends to make it a difficult development target.
> -See http://lwn.net/Articles/289013/ for more information on this topic, and
> -stay tuned; much is still in flux where linux-next is involved.
> +Linux-next has become an integral part of the kernel development process;
> +all patchs merged during a given merge window should really have found
patches
> +their way into linux-next some time before the merge window opens.
> +
Apart from that, looks great to me :)
Best regards,
Nicolas Kaiser
next prev parent reply other threads:[~2011-03-25 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 18:30 [PATCH] docs: update the development process document Jonathan Corbet
2011-03-25 19:36 ` Nicolas Kaiser [this message]
2011-03-25 20:18 ` Greg KH
2011-03-25 22:00 ` Marcin Slusarz
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=20110325203607.05061aa2@absol.kitzblitz \
--to=nikai@nikai.net \
--cc=corbet@lwn.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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