At 10/18/2016 08:07 PM, David Sterba wrote:
On Thu, Oct 13, 2016 at 03:32:53PM +0800, Qu Wenruo wrote:
Hi David,
Any updates?
If you're busy on these fix, I could fix these problem and send a new
version.
I was about to add the series to merge but the output format needs work.
At minimum, something that's parseable, so some commonly used format
(yaml or json). The current way is ok for quick overview, but I'd really
like to see more options of the output. The malloc/free problems are
minor.
Thanks for the comment.
It makes sense. And it can be the first step to make all btrfs commands
output parseable.
I could try to use json-c as our json library to add json output mode
for send dump.
Meanwhile the original design for send-dump is only for human, and the
json output support will be a huge work(not only for send-dump, but
quite a lot of other sub-commands).
What about merge send dump first, and then add json support step-by-step?
Thanks,
Qu
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
