Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Working together
Date: Wed, 23 May 2001 09:51:42 +0000	[thread overview]
Message-ID: <20010523095142.A22671@sistina.com> (raw)
In-Reply-To: <OF97CFF081.B6DCBCCA-ON85256A50.004CE72A@raleigh.ibm.com>; from peloquin@us.ibm.com on Fri, May 18, 2001 at 09:01:49AM -0500

Mark,

we thank you for your invitation to join you with work on the EVMS
project.  Obviously we are interested in the work you are doing and
support it whole heartedly.

We will be happy to help you with any technical assistance you may need
with regard to the Linux LVM system.  However we do not feel able to commit a
developer to work full time on your project for various reasons:

o The LVM team is very small, consisting of three main developers, we
  really do not have much spare man power.

o EVMS, though heading in a direction that we like, is a long way from
  going into production.  Our priority must be with the existing LVM
  system, especially now 0.9 is approaching production level.

o Our new development for the 1.2/2.0 branches has cluster support as
  it's main goal.  This does not seem to be anywhere on your roadmap.

On a more positive note components of our work, such as the standalone
snapshot driver, will undoubtedly benefit both projects.  We will take
the time to ensure that your requirements are taken into consideration
when writing these.

Regards,
Heinz    -- The LVM Guy --


On Fri, May 18, 2001 at 09:01:49AM -0500, Mark Peloquin wrote:
> Hello everyone,
> 
> On behalf of the EVMS project (http://sourceforge.net/projects/evms or
> http://oss.software.ibm.com/developerworks/opensource/evms) team, we
> would like to invite the Linux LVM project to join/collaborate with our
> project.  The goal of this collaboration is to offer a complimentary set of
<SNIP>
> 
> We hope you will join us as we look forward to working with you.
> 
> Thanks.
> 
> The EVMS Team
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  parent reply	other threads:[~2001-05-23  9:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-18 14:01 [linux-lvm] Working together Mark Peloquin
2001-05-18 16:27 ` Heinz J. Mauelshagen
2001-05-20  5:44   ` Tracy R Reed
2001-05-21 14:58     ` Heinz J. Mauelshagen
2001-05-19 16:37 ` Matthew O'Keefe
2001-05-23  9:51 ` Heinz J. Mauelshagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-19 19:54 Mark Peloquin
2001-05-21 18:42 Ben Rafanello
2001-05-23 15:33 Mark Peloquin
2001-05-23 20:48 ` Heinz J. Mauelshagen

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=20010523095142.A22671@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.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