Hi,
We had a discussion with Linus off the list! I've just made a fix for the stuff
he didn't like, and I will probably put out a new patch tomorrow.
-- Dag
On Thu, 09 Nov 2000 15:07:16 -0800, you wrote:
> Jean Tourrilhes wrote:
>
> > On Thu, Nov 09, 2000 at 10:33:39AM +0000, Dag Brattli wrote:
>
> <snip>
>
> > For now, let's keep the status-quo. Let's keep Linux-IrDA as a
> > big patch against the kernel. Applying a patch is not much more tricky
> > than compiling a standalone package, and it minimse the work you have
> > to do. Do a small do explaining how to get IrDA up and running.
> > Then, I expect Alan to take over the maintainance of 2.4 when
> > Linus will for 2.5. Alan has always done a superb job with respect to
> > kernel maintainance, and has always been receptive to your
> > patches. So, at this point, you create a nice diff, with changelog,
> > send it to the kernel mailing list and ...
> >
> >
> >> So should we make our own Linux-IrDA package, or should we stay within the
> >> kernel distribution? Currently we don't need any modifications within the Linux
> >> kernel itself.
> >
> >
> > Keep the current process for now. Just post regular patches on
> > SourceForge. By the way, why the latest patch has not been uploaded on
> > source forge ?
>
> IMVHO,
>
> It seems to me that some respected kernel hackers could do a code review
> of the big patch. If nothing really heinous is found, the big patch
> could go into the kernel tree. I think this would raise the amount of
> testing the code gets and also increase the visibility of the code, thus
> increasing code review feedback. Linus mentioned seeing a specific
> problem in the first screenful of the big patch that he didn't like.
> I have seen no response to his critique. I think you need to respond
> quickly to any specific feedback you get to the big patch.
> My take it this: Since the IrDA code in the current kernel
> tree is busted and since the IrDA maintainer and development/tester
> community say that this big patch gets IrDA working, let's accept it
> and then shoot it full of holes if there are lots of design and
> kernel integration problems. The IrDA development team is now aware
> that CCing LKML and including detailed Changelogs is required.
> I'd rather be the kernel community be critiquing and testing code that
> at least works a bit.
>
> Miles
>
>
>
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
