On Wed, Mar 29, 2006 at 05:54:07PM -0300, Otavio Salvador wrote:
> Sven Luther <[EMAIL PROTECTED]> writes:
>
> >> The drawbacks that I can see:
> >>
> >> - when we need to update a module ('cause a security flaw or a
> >> serious bug) we'll need to recompile the whole kernel;
> >
> > - it is well adapted to ubuntu's centralized maintenance system, but less
> > adapted to debian's distributed nature. At least that was the concensus
> > here last time we spoke about the issue.
> >
> > Also, if i remember well, ubuntu has no testing, so they can't do the two
> > level archive we have, and let the testing scripts synchronize the modules
> > with the kernel.
>
> But what if every module maintainer to be a kernel-team member to work
> in his modules? Wouldn't be that hard to have it done. We might have a
> process to accept a module in tree but after that it start to be part
> of maintainence of kernel team itself.
>
> I just realised that it might be a good workaround for our current
> problems.
Well, what can i say, look at the mailing list archive for previous discussion
on this :)
Friendly,
Sven Luther
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
