From: Boaz Harrosh <bharrosh@panasas.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
James.Bottomley@suse.de, michaelc@cs.wisc.edu, konrad@darnok.org,
jeykholt@cisco.com, hare@suse.de, hch@lst.de,
James.Smart@Emulex.Com, andrew.vasquez@qlogic.com,
philipp.reisner@linbit.com, martin.petersen@oracle.com,
vasu.dev@linux.intel.com, Joel Becker <joel.becker@oracle.com>,
Linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [ANNOUNCE] TCM/LIO v4.0.0-rc4 for 2.6.36-rc4
Date: Sun, 19 Sep 2010 15:55:16 +0200 [thread overview]
Message-ID: <4C961644.70209@panasas.com> (raw)
In-Reply-To: <1284841932.13344.339.camel@haakon2.linux-iscsi.org>
On 09/18/2010 10:32 PM, Nicholas A. Bellinger wrote:
> On Sat, 2010-09-18 at 13:00 +0900, FUJITA Tomonori wrote:
> So the RFC cuts have been going into a seperate tree here:
>
> http://git.kernel.org/?p=linux/kernel/git/nab/lio-4.0.git;a=summary
>
This is the two weeks ago stuff, right. Where is the lio-core-2.6.git/ ?
> Mike has requested an RFC v2 for him to review TCM Core and TCM_Loop
> v4.0.0-rc4 changes. So I will be respinning this tree with the latest
> changes from lio-core-2.6.git/lio-4.0 and re-posting in the next days.
>
Me to. And a git tree and a git web, as well. I'll postpone any review
to that time.
Thanks
Boaz
next prev parent reply other threads:[~2010-09-19 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 20:22 [ANNOUNCE] TCM/LIO v4.0.0-rc4 for 2.6.36-rc4 Nicholas A. Bellinger
2010-09-18 4:00 ` FUJITA Tomonori
2010-09-18 20:32 ` Nicholas A. Bellinger
2010-09-19 13:55 ` Boaz Harrosh [this message]
2010-09-20 9:18 ` Nicholas A. Bellinger
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=4C961644.70209@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@suse.de \
--cc=James.Smart@Emulex.Com \
--cc=andrew.vasquez@qlogic.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jeykholt@cisco.com \
--cc=joel.becker@oracle.com \
--cc=konrad@darnok.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=philipp.reisner@linbit.com \
--cc=vasu.dev@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.