From: Andi Kleen <ak@suse.de>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Writing linux kernel specification
Date: 24 Oct 2004 01:56:11 +0200 [thread overview]
Message-ID: <p73acud7zvo.fsf@verdi.suse.de> (raw)
In-Reply-To: <417AE4EA.6070107@bigpond.net.au.suse.lists.linux.kernel>
Peter Williams <pwil3058@bigpond.net.au> writes:
> Maybe that (the mostly bit) is what needs to be documented/specified
> i.e. any differences between the Linux user space ABI and those two
> standards. Surely that difference is reasonably stable and having it
> documented in a single place would be useful.
Andries Brouwer's linux manpages did exactly that for many years.
Of course there are sometimes mistakes and bugs in them, but
he accepts patches.
-Andi
next parent reply other threads:[~2004-10-23 23:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0410231118570.25612-100000@chimarrao.boston.redhat.com.suse.lists.linux.kernel>
[not found] ` <417AE4EA.6070107@bigpond.net.au.suse.lists.linux.kernel>
2004-10-23 23:56 ` Andi Kleen [this message]
2004-10-23 13:39 Writing linux kernel specification Karel Kulhavy
2004-10-23 13:54 ` Lars Marowsky-Bree
2004-10-23 14:01 ` Måns Rullgård
2004-10-23 15:20 ` Rik van Riel
2004-10-23 23:10 ` Peter Williams
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=p73acud7zvo.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pwil3058@bigpond.net.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.