From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Arnd Bergmann" <arnd@arndb.de>, "Christoph Hellwig" <hch@lst.de>,
cbe-oss-dev@ozlabs.org, "Jeremy Kerr" <jk@ozlabs.org>,
linux-kernel@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: SCHED_IDLE documentation
Date: Mon, 3 Mar 2008 11:20:55 +0100 [thread overview]
Message-ID: <cfd18e0f0803030220w6bde288bo5ef085db8b3412e3@mail.gmail.com> (raw)
In-Reply-To: <20080303101751.GA21190@elte.hu>
On Mon, Mar 3, 2008 at 11:17 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Michael Kerrisk <mtk.manpages@googlemail.com> wrote:
>
>
> > > commit 0e6aca43e08a62a48d6770e9a159dbec167bf4c6
> > > Author: Ingo Molnar <mingo@elte.hu>
> > > Date: Mon Jul 9 18:51:57 2007 +0200
> >
> > Yep -- I found it later -- thanks.
> >
> > Ingo, could you please CC me when kernel-userland API changes go into
> > mainline? Otherwise, they potentially end up undocumented, and
> > un(der)used.
>
> sure.
>
> We could also add an in-commit-message marker for such changes, that you
> could periodically scan. Something like:
>
> User-ABI-extended-by: Ingo Molnar <mingo@elte.hu>
>
> and:
>
> User-ABI-modified-by: Ingo Molnar <mingo@elte.hu>
>
> that way you also know whom to contact about followup questions.
>
> Declaring such changes would have other benefits as well: the review
> process becomes more streamlined. Also, any ABI side-effect would be
> known to be intentional versus unintentional, based on the commit
> headers alone. Undeclared ABI side-effects would be frowned upon and
> would be strong grounds for immediate reversal as well.
Sounds like an excellent idea, if we could make it fly. How can we make it fly?
Cheers,
Michael
--
Michael Kerrisk
Maintainer of the Linux man-pages project
http://www.kernel.org/doc/man-pages/
Want to report a man-pages bug? Look here:
http://www.kernel.org/doc/man-pages/reporting_bugs.html
next prev parent reply other threads:[~2008-03-03 10:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1203376368.275756.252634247263.1.gpush@pokey>
[not found] ` <200803030612.28039.arnd@arndb.de>
[not found] ` <20080303051719.GA26102@lst.de>
2008-03-03 6:21 ` Arnd Bergmann
2008-03-03 7:33 ` Ingo Molnar
2008-03-03 8:40 ` Michael Kerrisk
2008-03-03 9:24 ` Ingo Molnar
2008-03-03 9:31 ` Arnd Bergmann
2008-03-03 10:03 ` Michael Kerrisk
2008-03-03 10:04 ` Ingo Molnar
2008-03-03 10:12 ` Michael Kerrisk
2008-03-03 10:07 ` Michael Kerrisk
2008-03-03 10:17 ` Ingo Molnar
2008-03-03 10:20 ` Michael Kerrisk [this message]
2008-03-03 12:31 ` Michael Kerrisk
2008-03-03 12:52 ` Ingo Molnar
2008-03-03 14:06 ` Michael Kerrisk
2008-03-04 11:11 ` Peter Zijlstra
2008-03-05 15:19 ` Michael Kerrisk
2008-03-03 14:42 ` Michael Kerrisk
2008-03-05 15:02 ` Michael Kerrisk
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=cfd18e0f0803030220w6bde288bo5ef085db8b3412e3@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=hch@lst.de \
--cc=jk@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome