linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Nilesh Borate" <nilesh.borate@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Re: Writing LVM2 specific testcase.
Date: Wed, 28 Feb 2007 14:38:53 +0530	[thread overview]
Message-ID: <b73199e30702280108ob4fe46ai2ce7892ada55c884@mail.gmail.com> (raw)
In-Reply-To: <b73199e30702260700l5ad2cda6l27458d49149bd33e@mail.gmail.com>

Any guidelines !

On 2/26/07, Nilesh Borate <nilesh.borate@gmail.com> wrote:
> Hi,
>
>
>
> I am testing LVM2 package. I am already done with a lvm testcase which
> simply runs most of the the lvm commands on loop devices, and checks
> for each commands exit value.
>
> But I want to build a LVM2 specific
> testcase. I want to figure out exact differences of LVM2 from LVM1,
> and how should I proceed with LVM2 specific tests.
>
> Any guidelines, help would be of definite help.
>
> Thanks & Warm Regards,
>
>
> Nilesh C. Borate
>

      reply	other threads:[~2007-02-28  9:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 15:00 [linux-lvm] Writing LVM2 specific testcase Nilesh Borate
2007-02-28  9:08 ` Nilesh Borate [this message]

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=b73199e30702280108ob4fe46ai2ce7892ada55c884@mail.gmail.com \
    --to=nilesh.borate@gmail.com \
    --cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).