From: Jon Masters <jonathan@jonmasters.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: ANNOUNCE: LKML Summary Podcast
Date: Mon, 04 May 2009 10:08:15 -0400 [thread overview]
Message-ID: <1241446095.7268.6.camel@jcmlaptop> (raw)
Folks,
I'm /experimenting/ with recording a short 3-5 minute summary of LKML
traffic for those of us who like to listen to Podcasts. It's modeled
after e.g. the NYT Front Page Podcast, though not quite as cool.
I am hoping this of use to some people who can't read LKML every day.
Yesterday took 15-20 minutes to put together, and that's doable on a
regular basis, subject to it being of use to anyone. I figured I'm
reading LKML whether I do I summary recording or not. If it takes off,
then I'll try forming a small team to share the effort out.
Podcast: http://podcasts.jonmasters.org/kernel/kernel.xml
(it'll show up in iTunes shortly for those with iPhones)
Jon.
next reply other threads:[~2009-05-04 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 14:08 Jon Masters [this message]
2009-05-05 19:52 ` ANNOUNCE: LKML Summary Podcast Jeff Garzik
2009-05-05 20:33 ` Jon Masters
2009-05-05 21:42 ` Frederic Weisbecker
2009-05-11 17:07 ` Jon Masters
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=1241446095.7268.6.camel@jcmlaptop \
--to=jonathan@jonmasters.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox