From: Theodore Ts'o <tytso@mit.edu>
To: Jiri Kosina <jikos@kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] cleaning up kthread freezer hell, part 2
Date: Sun, 10 Jul 2016 19:55:59 -0400 [thread overview]
Message-ID: <20160710235559.GN26097@thunk.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1607082030470.24757@cbobk.fhfr.pm>
On Sat, Jul 09, 2016 at 12:31:33AM +0200, Jiri Kosina wrote:
>
> The idea is to get as much coverage among high-profile maintainers as
> possible, in a hope that this will result in ultimate tree-wide cleanup of
> the current mess. That's why I propose this as a core topic rather than
> tech topic, although it might sound like a rather bordeline one.
It doesn't have to be either/or. One possibility is after doing a
discussion amonst the core developers about how to do the tree-wide
cleanup, you could also do a presentation during the tech sessions
about how not to screw up new users of the freezer.
Although we probably don't have the resources to get a profession
video made of tech talk session for which the goal is broad
dissemination of information (although if some company wants to
sponsor such a thing, or if someone wants to volunteer to do the video
taping where the presenter has given consent, please contact the me or
the program committee), I suspect getting an audio recording, which
plus the slides could easily get turned into something that could be
uploaded to You Tube, wouldn't be that hard.
- Ted
prev parent reply other threads:[~2016-07-10 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 22:31 Jiri Kosina
2016-07-08 23:19 ` Rafael J. Wysocki
2016-07-09 6:19 ` Julia Lawall
2016-07-09 12:44 ` Shuah Khan
2016-07-10 23:55 ` Theodore Ts'o [this message]
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=20160710235559.GN26097@thunk.org \
--to=tytso@mit.edu \
--cc=jikos@kernel.org \
--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