From: Dmitry Yusupov <dmitry_yus@yahoo.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-iscsi development team
<linux-iscsi-devel@lists.sourceforge.net>,
linux-iscsi-users@lists.sourceforge.net,
open-iscsi@googlegroups.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, dm-devel@redhat.com,
iscsitarget-devel@lists.sourceforge.net, itn780@yahoo.com,
mikenc@us.ibm.com, cnitin@cisco.com, smithan@cisco.com,
coughlan@redhat.com, alewis@redhat.com, mbasavai@cisco.com,
andmike@us.ibm.com, Ming Zhang <mingz@ele.uri.edu>
Subject: Re: [linux-iscsi-devel] [ANNOUNCE] open-iscsi and linux-iscsi project teams have merged!
Date: Thu, 14 Apr 2005 09:18:32 -0700 [thread overview]
Message-ID: <1113495512.13939.75.camel@beastie> (raw)
In-Reply-To: <20050414111624.GA24570@lst.de>
On Thu, 2005-04-14 at 13:16 +0200, Christoph Hellwig wrote:
> On Mon, Apr 11, 2005 at 10:30:58PM -0400, linux-iscsi development team wrote:
> > The linux-iscsi and open-iscsi developers would like to announce
> > that they have combined forces on a single iSCSI initiator effort!
>
> What SCM will the code be in? I must admit I really, really prefer the
> SVN hosting of open-iscsi over the sf.net CVS mess.
Consider linux-iscsi-5.x CVS branch as a "mainline". Current open-iscsi
SVN repository is the place where all hard-core development will happen
at least for the nearest future.
I really hope sf.net will provide SVN hosting very soon. than we will
see how it goes. and may be we might just migrate current berlios.de
hosting to the sf.net.
next prev parent reply other threads:[~2005-04-14 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 2:30 [ANNOUNCE] open-iscsi and linux-iscsi project teams have merged! linux-iscsi development team
2005-04-14 11:16 ` [linux-iscsi-devel] " Christoph Hellwig
2005-04-14 16:18 ` Dmitry Yusupov [this message]
2005-04-14 16:19 ` Christoph Hellwig
2005-04-14 16:48 ` Lee Revell
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=1113495512.13939.75.camel@beastie \
--to=dmitry_yus@yahoo.com \
--cc=alewis@redhat.com \
--cc=andmike@us.ibm.com \
--cc=cnitin@cisco.com \
--cc=coughlan@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=iscsitarget-devel@lists.sourceforge.net \
--cc=itn780@yahoo.com \
--cc=linux-iscsi-devel@lists.sourceforge.net \
--cc=linux-iscsi-users@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mbasavai@cisco.com \
--cc=mikenc@us.ibm.com \
--cc=mingz@ele.uri.edu \
--cc=open-iscsi@googlegroups.com \
--cc=smithan@cisco.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