From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, brand@jupiter.cs.uni-dortmund.de
Cc: brand@eeyore.valparaiso.cl, linux-kernel@vger.kernel.org
Subject: Re: syscall documentation
Date: Fri, 7 Feb 2003 19:18:36 +0100 (MET) [thread overview]
Message-ID: <UTC200302071818.h17IIaJ29578.aeb@smtp.cwi.nl> (raw)
> How about saying in CONFORMING TO
Done.
> And as this was during the current development series,
> what is the point of manpages anyway?
Historical documentation is also useful.
And the page contains a reference to hugetlbfs, which
is not obsolete.
And 2.4.20 contains the names (with ENOSYS) - no doubt
some people will wonder what they are.
Andries
[If you have recent man pages, try "man ttyslot"]
next reply other threads:[~2003-02-07 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 18:18 Andries.Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-06 20:05 Andries.Brouwer
2003-02-07 16:31 ` Horst von Brand
2003-02-10 2:09 ` Jeff Garzik
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=UTC200302071818.h17IIaJ29578.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=brand@eeyore.valparaiso.cl \
--cc=brand@jupiter.cs.uni-dortmund.de \
--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®