From: <Administrator@gplvpartners.net>
To: <akpm@osdl.org>
Cc: <dgc@sgi.com>, <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>
Subject: [MailServer Notification]Attachment Blocking Notification
Date: Mon, 20 Mar 2006 23:38:43 +0100 [thread overview]
Message-ID: <001c01c64c6f$0ac39af0$040010ac@lutech.lan> (raw)
The dirty-buffers.sh has been blocked,
and Quarantine entire message has been taken on 3/20/2006 11:38:28 PM.
Message details:
Server:IMIW007CM
Sender: leo@strike.wu-wien.ac.at;
Recipient:akpm@osdl.org;dgc@sgi.com;linux-kernel@vger.kernel.org;linux-fsdevel@vger.kernel.org;
Subject:Re: [PATCH] Prevent large file writeback starvation
Attachment name:dirty-buffers.sh
next reply other threads:[~2006-03-20 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 22:38 Administrator [this message]
2006-03-21 17:49 Administrator
2006-07-21 19:17 scanmail
2007-09-27 20:24 Administrator
2008-07-15 0:00 Administrator
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='001c01c64c6f$0ac39af0$040010ac@lutech.lan' \
--to=administrator@gplvpartners.net \
--cc=akpm@osdl.org \
--cc=dgc@sgi.com \
--cc=linux-fsdevel@vger.kernel.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
Powered by JetHome