From: "Randy.Dunlap" <rddunlap@osdl.org>
To: John Levon <movement@marcelothewonderpenguin.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
<george@mvista.com>
Subject: Re: [PATCH 6/6] High-res-timers part 6 (support-man) take 2
Date: Mon, 30 Sep 2002 11:14:03 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33L2.0209301054310.4649-100000@dragon.pdx.osdl.net> (raw)
In-Reply-To: <20020928182014.GA56265@compsoc.man.ac.uk>
On Sat, 28 Sep 2002, John Levon wrote:
| On Sat, Sep 28, 2002 at 10:32:08AM -0700, george anzinger wrote:
|
| > The 4th, 5th, and 6th parts are support code and not really
| > part of the kernel.
|
| So ...
|
| > This part contains man pages for the new system calls.
|
| ... why are they here ?
|
| http://freshmeat.net/projects/man-pages/
I agree, please let's not clutter the kernel tree.
--
~Randy
next prev parent reply other threads:[~2002-09-30 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 17:32 [PATCH 6/6] High-res-timers part 6 (support-man) take 2 george anzinger
2002-09-28 18:20 ` John Levon
2002-09-28 19:14 ` george anzinger
2002-09-30 18:14 ` Randy.Dunlap [this message]
2002-09-30 21:15 ` george anzinger
2002-09-30 21:21 ` Randy.Dunlap
2002-09-30 23:27 ` John Levon
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=Pine.LNX.4.33L2.0209301054310.4649-100000@dragon.pdx.osdl.net \
--to=rddunlap@osdl.org \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=movement@marcelothewonderpenguin.com \
/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;
as well as URLs for NNTP newsgroup(s).