On Tue, Feb 10, 2004 at 12:13:08PM -0500, Joey Hess wrote:
> > I'd like to split this up into common-2.2, common-2.4, common-2.6 so
> > that various module renames can be handled sanely.
> I have been trying to think of a way that wouldn't be specific to
> 2.4/2.6, since module renames happen in
Jeff Bailey wrote:
> In linux-kernel-di/modules/common, everything is done with the
> assumption of a 2.4 kernel.
>
> I'd like to split this up into common-2.2, common-2.4, common-2.6 so
> that various module renames can be handled sanely.
>
> This does mean that new module lists will need to be
On Mon, Feb 09, 2004 at 11:57:08PM -0500, Jeff Bailey wrote:
> In linux-kernel-di/modules/common, everything is done with the
> assumption of a 2.4 kernel.
>
> I'd like to split this up into common-2.2, common-2.4, common-2.6 so
> that various module renames can be handled sanely.
>
> This does m
In linux-kernel-di/modules/common, everything is done with the
assumption of a 2.4 kernel.
I'd like to split this up into common-2.2, common-2.4, common-2.6 so
that various module renames can be handled sanely.
This does mean that new module lists will need to be added in 3 places.
Thoughts?
Tk
4 matches
Mail list logo