From: Dave Wysochanski <dwysocha@redhat.com>
To: LVM2 development <lvm-devel@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
linux-lvm <linux-lvm@redhat.com>
Subject: [linux-lvm] Any exiisting users of existing LVM2 command line library interface (lvm2cmd.h)?
Date: Tue, 11 Sep 2007 10:32:26 -0400 [thread overview]
Message-ID: <1189521146.4451.17.camel@linux-cxyg> (raw)
A new LVM2 API library is in progress.
If you are an existing user of the current command line library
interface or are interested in a new LVM2 library, we're interested to
hear input:
1) how you are currently using the existing interface
2) what you would like to see in the new interface
Thanks.
next reply other threads:[~2007-09-11 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 14:32 Dave Wysochanski [this message]
2007-09-11 14:40 ` [linux-lvm] Any exiisting users of existing LVM2 command line library interface (lvm2cmd.h)? James Parsons
2007-09-11 17:29 ` Dave Wysochanski
2007-09-17 21:11 ` Alasdair G Kergon
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=1189521146.4451.17.camel@linux-cxyg \
--to=dwysocha@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=lvm-devel@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).