Re: using bug reports on vendor kernels

[Bill Rugolsky Jr.]

On Thu, Aug 09, 2001 at 10:46:35PM +0100, Arjan van de Ven wrote:
> On Thu, Aug 09, 2001 at 05:34:59PM -0400, Bill Rugolsky Jr. wrote:
> 
> > The real question is why not include the documentation with the patch?
> > As Linus will probably tell you, patch is pretty smart about stripping out stray
> > commentary, e.g.,
> > 
> > 	patch -p1 < ~/mail/apply
> > 
> 
> Doesn't help the people who don't want to look at all the patches but just
> want an overview.... and the spec file where the patches are applied does
> have (mostly 1 liners) documentation.

Well, my point is that the person creating the patch or adding it to the kernel
should document it, thereby distributing the work.  If formatted as a standard
header, one could pull it all out with a favorite text processing tool,
sed ... perl, and put it in a file, in say
/usr/share/doc/kernel*/rh-patch-descriptions. :-)

Regards,

   Bill Rugolsky