On 11/14/05, Arjan van de Ven <[email protected]> wrote:
>
> > > The process is like maintaining any other part of the kernel:
> > > - Try to make sure it works on all releases (harder to do with a full
> > > arch, I know, but not impossible.)
> >
> > Does this include all the rc releases? and the 2.6.14.x releases?
> >
> > > - keep it up to date with bugfixes and the such
> >
> > So the process is: when kernel release a new version, we should
> > update our arch related files to the new kernel, then send you the
> > patch. Am I right?
>
> well the idea is that you fix things BEFORE the kernel is released for
> final, so that the final releases work out of the box (well out of
> kernel.org). This implies that you sort of track the git tree on a
> regular basis, but at minimum look at the first -rc kernel.
yep, that's our plan. And for the 2.6.14.1, 2.6.14.2... versions, do
we have to follow every of them?
>
>
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
