public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: greg@kroah.com, akpm@linux-foundation.org, rdunlap@xenotime.net,
	joe@perches.com
Subject: [RFC]A question about kernel's development
Date: Tue, 22 Mar 2011 11:33:14 +0800	[thread overview]
Message-ID: <20110322033312.GA2219@gmail.com> (raw)

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.

             reply	other threads:[~2011-03-22  3:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22  3:33 Harry Wei [this message]
2011-03-22  3:51 ` [RFC]A question about kernel's development Steven Rostedt
2011-03-22  5:44   ` Harry Wei
2011-03-22  3:56 ` Greg KH
2011-03-22  5:46   ` Harry Wei

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=20110322033312.GA2219@gmail.com \
    --to=jiaweiwei.xiyou@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=joe@perches.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