From: Christoph Hellwig <hch@infradead.org>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] aeventd logging application (Part 1)
Date: Fri, 13 Feb 2004 23:04:51 +0000 [thread overview]
Message-ID: <20040213230451.C21467@infradead.org> (raw)
In-Reply-To: <547AF3BD0F3F0B4CBDC379BAC7E4189F2552B9@otce2k03.adaptec.com>; from mark_salyzyn@adaptec.com on Fri, Feb 13, 2004 at 05:40:43PM -0500
On Fri, Feb 13, 2004 at 05:40:43PM -0500, Salyzyn, Mark wrote:
> Excuse my (faked?) ignorance; I would like a good place to put this :-)
> Any suggestions on a suitable release mechanism?
>
> I will accept `on Adaptec media' ...
Adaptec website with an url in the driver source? I'm sure the distribution
vendors will pick it up for their next releases.
next prev parent reply other threads:[~2004-02-13 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 22:40 [PATCH] aeventd logging application (Part 1) Salyzyn, Mark
2004-02-13 23:04 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 21:48 Salyzyn, Mark
2004-02-13 22:04 ` James Bottomley
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=20040213230451.C21467@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
/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