From: Steve Kenton <skenton@ou.edu>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.63 Nasssty little hobbitsses making ssso many
Date: Thu, 27 Feb 2003 09:55:08 -0600 [thread overview]
Message-ID: <3E5E34DC.A4F39BCC@ou.edu> (raw)
>From the look of the BK snapshot they *are* being integrated.
Linus probably knows better than anyone the problems this causes.
I think he's right, documentation both internal and external is
important if things are to mature. Some will never want to fix
this sort of thing because it gets in the way of "real work" but
if it's going to be done it should be done before the next fork.
Steve
> Yes, I know this is a lot of work. But as it stands, it is a lot of
> _wasted_ work if the patches aren't being integrated.
reply other threads:[~2003-02-27 15:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E5E34DC.A4F39BCC@ou.edu \
--to=skenton@ou.edu \
--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