From: Gris Ge <fge@redhat.com>
To: dm-devel@redhat.com
Subject: [multipath] Should we include python API in the codebase?
Date: Fri, 23 Mar 2018 23:26:55 +0800 [thread overview]
Message-ID: <20180323152655.GB2842@redhat.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 267 bytes --]
Hi Guys,
I created a python API of multipath using the JSON output of multipathd
like what we did C API -- libdmmp:
https://github.com/cathay4t/python-dmmp
Does upstream want it maintained in the codebase of multipath-tools?
Thanks.
--
Gris Ge
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2018-03-23 15:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180323152655.GB2842@redhat.com \
--to=fge@redhat.com \
--cc=dm-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