From: Nuno Silva <nuno.silva@vgertech.com>
To: Zack Brown <zbrown@tumblerings.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Taking a break from Kernel Traffic
Date: Wed, 08 Feb 2006 07:24:54 +0000 [thread overview]
Message-ID: <43E99CC6.5080909@vgertech.com> (raw)
In-Reply-To: <20060207184101.GL24430@tumblerings.org>
Zack Brown wrote:
> Hi folks,
>
> Kernel Traffic has had a bit of an erratic schedule lately, and I finally
> decided to take an official break from it, instead of doing the on-again
> off-again thing I've done for the past 6 months or longer. The lkml traffic
> has grown a lot over the years, and it's finally gotten to be too much for
> me, at least too much to continue KT in its current form. If I do start it
> again at some point, it will probably be quite different from what it has
> been until now.
Thanks for all your hard work. I'll miss KT.
Peace,
Nuno Silva
next prev parent reply other threads:[~2006-02-08 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 18:41 Taking a break from Kernel Traffic Zack Brown
2006-02-07 19:05 ` Michael Kerrisk
2006-02-07 19:25 ` Andrew Walrond
2006-02-10 8:07 ` Zack Brown
2006-02-08 7:24 ` Nuno Silva [this message]
2006-02-08 19:11 ` Jean Delvare
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=43E99CC6.5080909@vgertech.com \
--to=nuno.silva@vgertech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zbrown@tumblerings.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