From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Jeff Garzik <jeff@garzik.org>,
akpm@linux-foundation.org, linux-scsi@vger.kernel.org,
Andrew Vasquez <andrew.vasquez@qlogic.com>
Subject: RE: [patch 14/25] SCSI: use irq_handler_t where appropriate
Date: Sat, 26 May 2007 15:45:31 -0500 [thread overview]
Message-ID: <1180212331.3712.73.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <1180020111.3692.24.camel@mulgrave.il.steeleye.com>
On Thu, 2007-05-24 at 10:21 -0500, James Bottomley wrote:
> On Thu, 2007-05-24 at 10:28 -0400, Salyzyn, Mark wrote:
> > This is not just a maintainer's issue. We see the silent ACK treatment
> > all the time from all avenues of inspection whether they be maintainers,
> > illuminati, interested parties or JAFO. There is a little bit of a
> > volunteer in every one of us.
> >
> > Requiring the maintainer to be cc'd is a burden on the submitter, I do
> > not want to spank someone that comes up with a useful patch that fails
> > some bureaucratic litmus test. It is still a good idea, but lets try a
> > different tactic?
> >
> > James, you are a volunteer, so I can not require an increase in your
> > burden. But it would be 'nice' if you had a git tree that reported
> > pending approval (so that makes three persistent trees if I am correct,
> > scsi-misc-2.6, scsi-rc-fixes-2.6 and scsi-pending-2.6?). This way we can
> > tell that you saw it, and as a maintainer we can see a change even if we
> > missed the patch email. It does make it hard for the maintainer to
> > report *which* patch to approve, but he could do a blanket approval of
> > what he sees in the pending tree? AndrewM can tell that he no longer
> > needs to track the patch, as it is now the SCSI list's responsibility
> > once it is in the pending tree.
>
> We can certainly try that approach. Please note that scsi-pending-2.6
> will essentially be a quilt like tree (i.e. constantly rebasing) so it
> will be impossible to pull incrementally from it ... but you will be
> able to fetch from it and just check it out to give the patches an
> inspection/try out.
OK, this is basically done. I've set up the pending tree here:
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-pending-2.6.git;a=summary
Since it's wet out today, I also coded up a git update hook that emails
people who get patches into this tree and the maintainers nagging about
needed acks.
James
next prev parent reply other threads:[~2007-05-26 20:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 21:41 [patch 14/25] SCSI: use irq_handler_t where appropriate akpm
2007-05-23 22:07 ` Jeff Garzik
2007-05-23 22:16 ` Andrew Morton
2007-05-23 22:55 ` James Bottomley
2007-05-24 5:51 ` Jeff Garzik
2007-05-24 14:04 ` James Bottomley
2007-05-24 14:28 ` Salyzyn, Mark
2007-05-24 15:21 ` James Bottomley
2007-05-26 20:45 ` James Bottomley [this message]
2007-05-24 15:17 ` Randy Dunlap
2007-05-24 15:28 ` James Bottomley
2007-05-24 20:49 ` Jeff Garzik
2007-05-25 9:32 ` Stefan Richter
2007-05-25 9:06 ` Stefan Richter
2007-05-24 20:52 ` Jeff Garzik
2007-05-24 13:32 ` Salyzyn, Mark
2007-05-23 23:00 ` David Miller
2007-05-24 11:31 ` Andrew Vasquez
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=1180212331.3712.73.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.vasquez@qlogic.com \
--cc=jeff@garzik.org \
--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