* btrfs send <ro-snap-0> -p <ro-snap-1>
@ 2017-09-25 15:43 Christian Brauner
0 siblings, 0 replies; only message in thread
From: Christian Brauner @ 2017-09-25 15:43 UTC (permalink / raw)
To: Christian Brauner; +Cc: dsterba, linux-btrfs
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-09-25 15:43 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-09-25 15:43 btrfs send <ro-snap-0> -p <ro-snap-1> Christian Brauner
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.