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.
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: [email protected]
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.
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,
greg k-h
On Mon, Mar 21, 2011 at 11:51:48PM -0400, Steven Rostedt 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.
>
> Well, a quick answer is that when we fix a bug, we tag it with
> Cc: [email protected]
>
> Then when it is applied to Linus's tree, Greg then can choose to pull it
> into the stable branch.
Yeah, it is true.
>
> 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 ;)
Hmmm, so we should learn all the details, which can
ease maintainers' burden.
Steven, thanks for your help.
Thanks.
Best Regards.
Harry Wei.
>
> -- 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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/