From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: John Stoffel <john@stoffel.org>, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: SCSI git trees
Date: Mon, 03 Aug 2009 19:00:08 +0000 [thread overview]
Message-ID: <1249326008.3943.210.camel@mulgrave.site> (raw)
In-Reply-To: <20090803110911.37044826.randy.dunlap@oracle.com>
On Mon, 2009-08-03 at 11:09 -0700, Randy Dunlap wrote:
> On Mon, 3 Aug 2009 13:52:29 -0400 John Stoffel wrote:
>
> > >>>>> "James" == James Bottomley <James.Bottomley@HansenPartnership.com> writes:
> >
> > James> It seems I got unsubscribed from linux-scsi last week while I was on
> > James> holiday and I've likely missed a slew of patches, it seems like an
> > James> appropriate time to remind everyone how the SCSI trees work.
> >
> > James> ---
> >
> > James> There are two git based scsi trees:
> >
> > James> http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git
> >
> > James> called the scsi-misc tree for patches being collected for the
> > James> next merge window. And
>
> James,
> Would it help you for patchwork to capture linux-scsi patches?
> either patchwork.kernel.org or patchwork.ozlabs.org
Well, SCSI was supposed to be one of the consumers of patchwork;
evidently we fell through the cracks.
However, it's not really going to help me that much because my MO is to
do most of my tree work offline (while travelling). Patchwork, being a
web based tool doesn't work well offline, so I need to keep on with my
email based workflow. (On the other hand evolution in its latest
incarnations is taking a very cavalier attitude to the "download
messages for offline use" flag ... if it gets much worse I'll lose my
offline work ability anyway).
James
next prev parent reply other threads:[~2009-08-03 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 17:07 SCSI git trees James Bottomley
2009-08-03 17:52 ` John Stoffel
2009-08-03 18:09 ` Randy Dunlap
2009-08-03 19:00 ` James Bottomley [this message]
2009-08-03 18:57 ` James Bottomley
2009-08-03 19:13 ` John Stoffel
2009-08-03 20:27 ` Jens Axboe
2009-08-03 21:00 ` John Stoffel
2009-08-03 21:04 ` Jens Axboe
2009-08-04 16:37 ` John Stoffel
2009-08-04 20:15 ` Jens Axboe
2009-08-04 20:27 ` John Stoffel
2009-08-04 20:36 ` Jens Axboe
2009-08-04 20:45 ` John Stoffel
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=1249326008.3943.210.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=john@stoffel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=randy.dunlap@oracle.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