From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "Peter Hüwe" <PeterHuewe@gmx.de>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Follow-Up(s) on previous Kernel Summits | KSummit Archive
Date: Sun, 12 Jul 2015 19:04:07 -0700 [thread overview]
Message-ID: <20150713020407.GP3717@linux.vnet.ibm.com> (raw)
In-Reply-To: <201507122355.20513.PeterHuewe@gmx.de>
On Sun, Jul 12, 2015 at 11:55:19PM +0200, Peter Hüwe wrote:
> Hi,
>
> I'm reading along ksummit-discuss for quite a while and I definitely see a lot
> of topics reoccurring each year -- also a lot of arguments and standpoints are
> similar each year :)
>
> Does it make sense to reserve a slot to revisit the topics of the previous KS,
> check their status and the agreed actions back then?
> Tinyfication, Stable Flow, 2038... just to name a few.
>
>
>
>
>
> And a bit related I just wanted to point to Paul McKenneys great summary of
> previous KSs:
>
> http://ftp.be.debian.org/pub/linux/kernel/people/paulmck/LKS/
And I do plan to summarize again this year. I was out last week, so have
not yet started. ;-)
Thanx, Paul
prev parent reply other threads:[~2015-07-13 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 21:55 [Ksummit-discuss] [CORE TOPIC] Follow-Up(s) on previous Kernel Summits | KSummit Archive Peter Hüwe
2015-07-13 2:04 ` Paul E. McKenney [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=20150713020407.GP3717@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=PeterHuewe@gmx.de \
--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 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.