From: Martin Bligh <mbligh@mbligh.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: william@brodie-tyrrell.org, Andrew Morton <akpm@osdl.org>,
linux-scsi@vger.kernel.org
Subject: Re: Fw: [Bugme-new] [Bug 6657] New: Domain validation failures on aic7xxx
Date: Mon, 12 Jun 2006 10:06:23 -0700 [thread overview]
Message-ID: <448D9F0F.4080106@mbligh.org> (raw)
In-Reply-To: <1150131252.3413.25.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Mon, 2006-06-12 at 09:47 -0700, Martin Bligh wrote:
>
>>It's not going to auto-forward, otherwise every update to bugs owned
>>by
>>the virtual alias will come through. What I was planning was to cc
>>linux-scsi on emails to bugme-new (ie one email per new bug only) for
>>that category only. I'll try to get that going this morning ...
>
>
> Yes ... that's what we want. An email that can be replied to and will
> go to the submitter and linux-scsi and be captured by bugzilla.
OK, set up. It should reply to bugme-daemon, which should result up
being back in the DB ... all emails should be tagged with [bugme-new]
in them, so its easy to filter if need be.
I cc'ed IO/storage-SCSI, and all the SCSI drivers ones. If that's not
correct, or you have other problems with it, let me know.
Hitting reply-all may result in mail to bugme-new as well as
bugme-daemon ... a mild pain, but should get caught by the list
filtration, so no big deal, I think.
M.
next prev parent reply other threads:[~2006-06-12 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 16:18 Fw: [Bugme-new] [Bug 6657] New: Domain validation failures on aic7xxx Andrew Morton
2006-06-10 16:26 ` James Bottomley
2006-06-12 16:47 ` Martin Bligh
2006-06-12 16:54 ` James Bottomley
2006-06-12 17:06 ` Martin Bligh [this message]
2006-06-13 10:52 ` William Brodie-Tyrrell
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=448D9F0F.4080106@mbligh.org \
--to=mbligh@mbligh.org \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=william@brodie-tyrrell.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