From: "Bill Rugolsky Jr." <rugolsky@ead.dsa.com>
To: Arjan van de Ven <arjan@fenrus.demon.nl>
Cc: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>,
linux-kernel@vger.kernel.org
Subject: Re: using bug reports on vendor kernels
Date: Thu, 9 Aug 2001 17:55:36 -0400 [thread overview]
Message-ID: <20010809175536.B22594@ead45> (raw)
In-Reply-To: <01080923020201.04501@idun> <m15Ux92-000PTaC@amadeus.home.nl> <20010809173459.A24128@ead45> <20010809224635.A19529@fenrus.demon.nl>
In-Reply-To: <20010809224635.A19529@fenrus.demon.nl>; from arjan@fenrus.demon.nl on Thu, Aug 09, 2001 at 10:46:35PM +0100
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
next prev parent reply other threads:[~2001-08-09 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 21:02 Oliver Neukum
2001-08-09 21:15 ` arjan
2001-08-09 21:34 ` Bill Rugolsky Jr.
2001-08-09 21:46 ` Arjan van de Ven
2001-08-09 21:55 ` Bill Rugolsky Jr. [this message]
2001-08-10 8:24 ` Ville Herva
2001-08-09 21:31 ` Andreas Dilger
2001-08-09 21:42 ` Oliver Neukum
2001-08-09 21:59 ` Bill Rugolsky Jr.
2001-08-10 9:42 ` Chmouel Boudjnah
2001-08-10 1:32 ` Ignacio Vazquez-Abrams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010809175536.B22594@ead45 \
--to=rugolsky@ead.dsa.com \
--cc=Oliver.Neukum@lrz.uni-muenchen.de \
--cc=arjan@fenrus.demon.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®