linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Thanos Makatos <thanos.makatos@onapp.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm filter regex format
Date: Tue, 19 Dec 2017 09:36:51 +0000	[thread overview]
Message-ID: <CAM2wQBvZUWocdwEfpO8F7+OdZEOzA8gWSb6YjBgZYFu7MR-0Ww@mail.gmail.com> (raw)
In-Reply-To: <20171218174915.snuf5ctm4ud5naye@reti>

> Out of interest why are you using the length of the device name as a discriminator?

In my case I am the one who creates these devices so I fully control
the naming scheme, however there are other components in our product
that might create device mapper targets and I shouldn't filter them
out.

  reply	other threads:[~2017-12-19  9:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 17:16 [linux-lvm] lvm filter regex format Thanos Makatos
2017-12-18 17:49 ` Joe Thornber
2017-12-19  9:36   ` Thanos Makatos [this message]
     [not found] <72381975.739900.1513623186634.ref@mail.yahoo.com>
2017-12-18 18:53 ` matthew patton
2017-12-18 22:43   ` Zdenek Kabelac
2017-12-19  8:51   ` Joe Thornber

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=CAM2wQBvZUWocdwEfpO8F7+OdZEOzA8gWSb6YjBgZYFu7MR-0Ww@mail.gmail.com \
    --to=thanos.makatos@onapp.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).