On Wednesday 27 March 2002 05:46, Greg KH wrote:
> On Tue, Mar 26, 2002 at 10:53:27AM -0800, Petko Manolov wrote:
> > Greg KH wrote:
> > >made the change and go complain to them.  However, 99% of the time
> > >you are usually very glad that the change was made, and you should
> > >not mind that other people are fixing your code.
> >
> > I don't mind when the api change and somebody make the driver compile.
> > It did happen people changing stuff they haven't even tested on a real
> > device though.
>
> That's why it's called a development kernel :)

I'm sorry, but I'm not buying that. Even on a development kernel there 
should be at least some form of testing except for the most trivial 
patches. If someone with a patch doesn't have the hardware/setup, then the 
first thing to do would is send it to the maintainer. Development doesn't 
mean you can just 'break' things...

> > I quite like Werner's aproach.  He made the fix for big endian
> > machines, tested it, but sent it to _me_ for aproval.  If a piece of
> > code is actively maintained it makes tons of sense to notify the
> > maintainer, isn't it?
>
> Yes it does, that's also what is spelled out in
> Documentation/SubmittingPatches

Then why does nobody do it? It's all I'm asking....

 - Nemosoft


-- 
Linux Philips webcam driver page: http://www.smcc.demon.nl/webcam/
Includes FAQs, links to working programs and lots of info.

_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to