From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Christoph Pleger <christoph.pleger@cs.uni-dortmund.de>
Subject: Re: [linux-lvm] Programming interface
Date: Wed, 21 Aug 2019 14:08:38 +0200 [thread overview]
Message-ID: <0d19c968-e9ff-599e-60fd-c83a96c2ea07@redhat.com> (raw)
In-Reply-To: <d665ffeb83394a4bf24835f901311db0@cs.uni-dortmund.de>
Dne 21. 08. 19 v 13:14 Christoph Pleger napsal(a):
> Hello,
>
>> The 'new' idea was to use/provide 'DBus' API - however it's also not a
>> lot of 'traction' :( and it's also missing lot of features and
>> design...
>
> Surely you are not saying that the dbus interface will also disappear -
> because I am using that in another, less complicated application, though not
> directly, but with libblockdev.
It's rather the issue of maintenance and keeping it 'up-to-date' with current
lvm2 - since there are already quite a few missing 'parts' to be encoded into
dbus...
Zdenek
next prev parent reply other threads:[~2019-08-21 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 7:58 [linux-lvm] Programming interface Christoph Pleger
2019-08-21 8:46 ` Zdenek Kabelac
2019-08-21 11:14 ` Christoph Pleger
2019-08-21 12:08 ` Zdenek Kabelac [this message]
2019-08-23 13:20 ` Christoph Pleger
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=0d19c968-e9ff-599e-60fd-c83a96c2ea07@redhat.com \
--to=zkabelac@redhat.com \
--cc=christoph.pleger@cs.uni-dortmund.de \
--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).