From: Christian Brauner <christian.brauner@canonical.com>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: btrfs send <ro-snap-0> -p <ro-snap-1>
Date: Mon, 25 Sep 2017 17:43:47 +0200 [thread overview]
Message-ID: <20170925154346.br5lznxy3hpfup57@gmail.com> (raw)
Hi guys,
It seems that btrfs v4.12.1 allows:
(1) btrfs send -p <ro-snap-1> <ro-snap-0>
but disallows
(2) btrfs send <ro-snap-0> -p <ro-snap-1>
Code-wise it assumes that <ro-snap-1> is always found at optind == 1. I was
about to patch this but I'm not sure which way we'd like to go with this:
Actually only allow (1) and block (2) properly or allow both. In any case, this
seems to me like a pretty serious regression and we'd like to get this settled
soon. :)
Thanks!
Christian
reply other threads:[~2017-09-25 15:43 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=20170925154346.br5lznxy3hpfup57@gmail.com \
--to=christian.brauner@canonical.com \
--cc=christian.brauner@ubuntu.com \
--cc=dsterba@suse.cz \
--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).