linux-kernel - Re: [PATCH] docs: update the development process document

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110325203607.05061aa2@absol.kitzblitz>
Date:	Fri, 25 Mar 2011 20:36:07 +0100
From:	Nicolas Kaiser <nikai@...ai.net>
To:	Jonathan Corbet <corbet@....net>
Cc:	linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com>,
	Randy Dunlap <rdunlap@...otime.net>
Subject: Re: [PATCH] docs: update the development process document

* Jonathan Corbet <corbet@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/