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-next>] [day] [month] [year] [list]
Message-ID: <20110322033312.GA2219@gmail.com>
Date:	Tue, 22 Mar 2011 11:33:14 +0800
From:	Harry Wei <jiaweiwei.xiyou@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	greg@...ah.com, akpm@...ux-foundation.org, rdunlap@...otime.net,
	joe@...ches.com
Subject: [RFC]A question about kernel's development

Hi us,
   I wanna know our kernel's development 
procedure for details. I just realize
when we get a stable release, we must 
merge trementous patches into kernel.
I often watch -rc kernels, -git kernels, 
, -mm kernels and know their promulgators.
But i don't know their relationships and
sequences for shaping stable ones.
   Okay, now we want to develop 2.6.38 
to 2.6.39. How many specific steps should we
do? In fact, i recognize some. But i want to 
understand all the concrete procedures. Could
anyone help me, thanks in advance.

Thanks.
Best Regards.
Harry Wei.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ