From: Tony Asleson <tasleson@redhat.com>
To: Michael Schmidt <schmidmt@gmail.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Tagging LVs with Python Bindings
Date: Wed, 08 Apr 2015 12:10:11 -0500 [thread overview]
Message-ID: <552560F3.5000801@redhat.com> (raw)
In-Reply-To: <CAKEq5nuS7vs02WjHq-dKiW-8iApT=vUqMFKWD8a=XSiHvNOotQ@mail.gmail.com>
On 04/08/2015 10:47 AM, Michael Schmidt wrote:
> Much appreciated. I'll integrated your fix into the build I have.
>
> I looked through Bugzilla and didn't see anything and decided it would be
> more straight forward to ask if there was an existing method to solve the
> problem before suggesting it was a bug.
Definitely a bug :-)
https://bugzilla.redhat.com/show_bug.cgi?id=1210020
Thanks!
-Tony
prev parent reply other threads:[~2015-04-08 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 17:08 [linux-lvm] Tagging LVs with Python Bindings Michael Schmidt
2015-04-07 20:54 ` Tony Asleson
2015-04-08 15:47 ` Michael Schmidt
2015-04-08 17:10 ` Tony Asleson [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=552560F3.5000801@redhat.com \
--to=tasleson@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=schmidmt@gmail.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).