From: Andy Lutomirski <luto@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC] ABI feature gates?
Date: Thu, 3 Aug 2017 21:15:52 -0700 [thread overview]
Message-ID: <CALCETrXHFSLQk5VaZsOA=pSPDW7uJ08Dg_oPLxHAw6pEnsGYwA@mail.gmail.com> (raw)
In-Reply-To: <20170804013010.GA425@kroah.com>
On Thu, Aug 3, 2017 at 6:30 PM, Greg KH <greg@kroah.com> wrote:
> On Thu, Aug 03, 2017 at 06:16:44PM -0700, Andy Lutomirski wrote:
>> I'm wondering if there are other models that could work. I think it
>> would be nice for us to be able to land a kernel in Linus tree and
>> still wait a while before stabilizing it. Rust, for example, has a
>> strict policy for this that seems to work quite well.
>
> What does Rust do here?
>
Rust has named unstable features. In order to use them, you need to
declare, with a special annotation, your desire to use the named
feature. You also need to be running a nightly build of Rust --
stable versions will refuse to compile code that requests unstable
features.
next prev parent reply other threads:[~2017-08-04 4:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 1:16 Andy Lutomirski
2017-08-04 1:30 ` Greg KH
2017-08-04 4:15 ` Andy Lutomirski [this message]
2017-08-04 5:08 ` Sergey Senozhatsky
2017-08-04 8:23 ` Daniel Vetter
2017-08-04 2:26 ` Theodore Ts'o
2017-08-04 3:27 ` Stephen Rothwell
2017-08-04 5:13 ` Julia Lawall
2017-08-04 14:20 ` Theodore Ts'o
2017-08-04 15:47 ` Julia Lawall
2017-08-04 8:42 ` Jiri Kosina
2017-08-04 8:53 ` Hannes Reinecke
2017-08-04 16:04 ` Greg KH
2017-08-04 17:14 ` Theodore Ts'o
2017-08-04 17:53 ` Greg KH
2017-08-04 22:52 ` Joe Perches
2017-08-09 20:06 ` Geert Uytterhoeven
2017-08-14 19:49 ` Steven Rostedt
2017-08-14 19:51 ` Linus Torvalds
2017-08-15 7:13 ` Julia Lawall
2017-08-04 8:57 ` Julia Lawall
2017-08-04 11:27 ` Michael Kerrisk (man-pages)
2017-08-09 0:00 ` NeilBrown
2017-08-09 11:54 ` Laurent Pinchart
2017-08-14 20:07 ` Steven Rostedt
2017-08-09 20:21 ` Linus Torvalds
2017-08-11 6:21 ` NeilBrown
2017-08-11 6:39 ` Linus Torvalds
2017-08-11 8:02 ` NeilBrown
2017-08-11 23:10 ` Linus Torvalds
2017-08-14 4:19 ` NeilBrown
2017-08-14 18:34 ` Linus Torvalds
2017-08-14 18:40 ` Linus Torvalds
2017-08-14 23:23 ` Andy Lutomirski
2017-08-15 0:54 ` Linus Torvalds
2017-08-15 16:11 ` Andy Lutomirski
2017-08-15 18:26 ` Michael Kerrisk (man-pages)
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='CALCETrXHFSLQk5VaZsOA=pSPDW7uJ08Dg_oPLxHAw6pEnsGYwA@mail.gmail.com' \
--to=luto@kernel.org \
--cc=greg@kroah.com \
--cc=ksummit-discuss@lists.linuxfoundation.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