archive mirror
 help / color / mirror / Atom feed
From: "" <>
To: David Teigland <>
Subject: Re: [linux-lvm] Suggestion: lvm2 filters lib needs to show some readable info for end user
Date: Thu, 15 Oct 2020 23:05:38 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hello David,

I don't know why I could use "git show 1fa48ba9d60ad34c5957b80024ef660ffb11161f" to 
see your patch, but I can't find the commit in "git log" output (in master branch).
And the related code also doesn't be changed in master branch.


On 7/21/20 1:54 AM, David Teigland wrote:
> On Mon, Jul 20, 2020 at 07:02:15PM +0800, wrote:
>> So, in my opinion, I suggest there should be some code improvement for
>> all filter failed info. Some filter failed debug log should convert from
>> debug level to standard output level.
> Yes, that's long standing annoyance, and it's simple to fix.  Added that
> in the branch below, but it needs some tests, and it should probably be
> used in some more places.

  parent reply	other threads:[~2020-10-15 15:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 11:02 heming.zhao
2020-07-20 17:54 ` David Teigland
2020-07-21  8:37   ` heming.zhao
2020-10-15 15:05   ` heming.zhao [this message]
2020-10-15 15:16     ` David Teigland
2020-10-15 15:40       ` heming.zhao

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: [linux-lvm] Suggestion: lvm2 filters lib needs to show some readable info for end user' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).