From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
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: Fri, 4 Aug 2017 13:27:46 +0200 [thread overview]
Message-ID: <CAKgNAkjnjVy9ZWGxhdux+FzCLnyxv-w+mHvBo+rwMx2jmEmoRg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1708041056510.2950@hadrien>
On 4 August 2017 at 10:57, Julia Lawall <julia.lawall@lip6.fr> wrote:
>
>
> On Fri, 4 Aug 2017, Jiri Kosina wrote:
>
>> On Thu, 3 Aug 2017, Theodore Ts'o wrote:
>>
>> > One way that we could try to make things better is by having some kind
>> > of semi-automated system which monitors changes in include/uapi/*.h in
>> > linux-next.
>>
>> It's unfortunately just uapi though, and for sysfs it's a bit more
>> difficult to define a pathname pattern to watch for.
>
> I think that Michael Kerrisk has a big list of regexps in this direction.
The list I have is not very big, and is rather unsophisticated (and
manually maintained). But it helps me spot some new features that I
would otherwise miss and that should be documented in the man pages.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2017-08-04 11:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 1:16 [Ksummit-discuss] [MAINTAINER TOPIC] ABI feature gates? Andy Lutomirski
2017-08-04 1:30 ` Greg KH
2017-08-04 4:15 ` Andy Lutomirski
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) [this message]
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=CAKgNAkjnjVy9ZWGxhdux+FzCLnyxv-w+mHvBo+rwMx2jmEmoRg@mail.gmail.com \
--to=mtk.manpages@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=luto@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 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.