From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Taking a break from Kernel Traffic
Date: Tue, 7 Feb 2006 19:25:00 +0000 [thread overview]
Message-ID: <200602071925.00786.andrew@walrond.org> (raw)
In-Reply-To: <20060207184101.GL24430@tumblerings.org>
Whilst always lurking here, I have nonetheless found your summaries useful and
enjoyable, often highlighting important stuff I had completely missed or not
understood.
Will you still be doing "Zacks Kernel News" in a certain linux mag? Always the
most important section ;)
Best luck with whatever occupies your time now.
Andrew Walrond
next prev parent reply other threads:[~2006-02-07 19: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 [this message]
2006-02-10 8:07 ` Zack Brown
2006-02-08 7:24 ` Nuno Silva
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=200602071925.00786.andrew@walrond.org \
--to=andrew@walrond.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 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.