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: <20110322035148.GM14675@home.goodmis.org>
Date:	Mon, 21 Mar 2011 23:51:48 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org, greg@...ah.com,
	akpm@...ux-foundation.org, rdunlap@...otime.net, joe@...ches.com
Subject: Re: [RFC]A question about kernel's development

On Tue, Mar 22, 2011 at 11:33:14AM +0800, Harry Wei wrote:
> 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.

Well, a quick answer is that when we fix a bug, we tag it with
 Cc: stable@...nel.org

Then when it is applied to Linus's tree, Greg then can choose to pull it
into the stable branch.

I also believe that Greg spends lots of lonely nights looking into git
commits, drinking his favorite Latte and cursing at all the git patches
that fix a bug that didn't have a Cc: stable tag attached. He use to
have a huge mane of hair on his head before taking over as stable
maintainer ;)

-- Steve

>    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.
--
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