From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [RFC PATCH 0/3] btrfs-progs: make quiet to overrule verbose
Date: Thu, 24 Oct 2019 14:28:22 +0800 [thread overview]
Message-ID: <20191024062825.13097-1-anand.jain@oracle.com> (raw)
When both the options (--quiet and --verbose) in btrfs send and receive
is specified, we need at least one of it to overrule the other, irrespective
of the chronological order of options.
This patch-set makes quiet overrule verbose.
I don't think this shall break any script as such, because these two options are
of kind of mutually exclusive. But just in case if I am missing something? So
marked it as RFC.
And again patch 3/3 makes quiet option really quiet in receive and removes the
output
At snapshot <>
I don't expect scripts to specify quiet option and expect some logs.
Anand Jain (3):
btrfs-progs: send: let option quiet overrule verbose
btrfs-progs: receive: let option quiet overrule verbose
btrfs-progs: receive: make quiet really quiet
cmds/receive.c | 9 +++++++--
cmds/send.c | 6 +++++-
2 files changed, 12 insertions(+), 3 deletions(-)
--
2.23.0
next reply other threads:[~2019-10-24 6:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 6:28 Anand Jain [this message]
2019-10-24 6:28 ` [RFC PATCH 1/3] btrfs-progs: send: let option quiet overrule verbose Anand Jain
2019-10-24 6:28 ` [RFC PATCH 2/3] btrfs-progs: receive: " Anand Jain
2019-10-24 6:28 ` [RFC PATCH 3/3] btrfs-progs: receive: make quiet really quiet Anand Jain
2019-10-24 15:41 ` [RFC PATCH 0/3] btrfs-progs: make quiet to overrule verbose David Sterba
2019-10-24 23:51 ` Anand Jain
2019-10-25 1:56 ` Anand Jain
2019-10-25 16:35 ` David Sterba
2019-10-26 1:01 ` Anand Jain
2019-10-29 19:42 ` Anand Jain
2019-11-01 15:18 ` David Sterba
2019-11-04 6:26 ` Anand Jain
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=20191024062825.13097-1-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
/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).