From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: seven <horia.muntean@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Temporary random kernel hang
Date: Fri, 15 Dec 2006 11:54:40 +0100 [thread overview]
Message-ID: <1166180080.32332.236.camel@twins> (raw)
In-Reply-To: <7883193.post@talk.nabble.com>
On Thu, 2006-12-14 at 15:07 -0800, seven wrote:
>
> Andrew Morton wrote:
> >
> > No, I wasn't ignoring you for four days. Please, always do reply-to-all.
> >
>
> I am using nabble's interface to post messages ( www.nabble.com ) and I am
> not subscribed to the mailing list, so it's possible that this is the cause
> of the direct mail.
However, all these replies are send to your gmail account, so you
_could_ just 'reply to all' there, right?
Please do, finding lone responses on lkml is hard.
next prev parent reply other threads:[~2006-12-15 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 10:38 Temporary random kernel hang seven
2006-12-10 7:07 ` Andrew Morton
2006-12-11 18:46 ` seven
2006-12-14 22:10 ` Andrew Morton
2006-12-14 23:07 ` seven
2006-12-15 10:54 ` Peter Zijlstra [this message]
2006-12-15 12:06 ` seven
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=1166180080.32332.236.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=horia.muntean@gmail.com \
--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