ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: ksummit-discuss@lists.linuxfoundation.org,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: [Ksummit-discuss] [CORE TOPIC] Follow-Up(s) on previous Kernel Summits | KSummit Archive
Date: Sun, 12 Jul 2015 23:55:19 +0200	[thread overview]
Message-ID: <201507122355.20513.PeterHuewe@gmx.de> (raw)

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/


Thanks,
Peter

             reply	other threads:[~2015-07-12 21:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12 21:55 Peter Hüwe [this message]
2015-07-13  2:04 ` Paul E. McKenney

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=201507122355.20513.PeterHuewe@gmx.de \
    --to=peterhuewe@gmx.de \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=paulmck@linux.vnet.ibm.com \
    /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