From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC]A question about kernel's development
Date: Tue, 22 Mar 2011 13:46:22 +0800 [thread overview]
Message-ID: <20110322054619.GB2856@gmail.com> (raw)
In-Reply-To: <20110322035646.GA17601@kroah.com>
On Mon, Mar 21, 2011 at 08:56:46PM -0700, Greg KH wrote:
> 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.
> > 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.
>
> Please read Documentation/HOWTO and Documentation/development_process/
> for all of the details.
>
> If you have specific questions after reading all of that, please let us
> know.
Thanks, i will :)
Thanks.
Best Regards.
Harry Wei.
>
> thanks,
>
> greg k-h
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2011-03-22 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 3:33 [RFC]A question about kernel's development Harry Wei
2011-03-22 3:51 ` Steven Rostedt
2011-03-22 5:44 ` Harry Wei
2011-03-22 3:56 ` Greg KH
2011-03-22 5:46 ` Harry Wei [this message]
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=20110322054619.GB2856@gmail.com \
--to=jiaweiwei.xiyou@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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