From: David Sterba <dsterba@suse.cz>
To: Christoph Heiss <christoph@c8h4.io>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 5/7] btrfs-progs: subvol list: implement json format output
Date: Thu, 17 Aug 2023 21:59:46 +0200 [thread overview]
Message-ID: <20230817195946.GV2420@twin.jikos.cz> (raw)
In-Reply-To: <20230813094555.106052-6-christoph@c8h4.io>
On Sun, Aug 13, 2023 at 11:45:00AM +0200, Christoph Heiss wrote:
> Implements JSON-formatted output for the `subvolume list` command using
> the `--format json` global option, much like it is implemented for other
> commands.
>
> Re-uses the `btrfs_list_layout` infrastructure to nicely fit it into the
> existing formatting code.
>
> A notable difference to the normal, text-based output is that in the
> JSON output, timestamps include the timezone offset as well.
>
> Signed-off-by: Christoph Heiss <christoph@c8h4.io>
> ---
> cmds/subvolume-list.c | 91 +++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 88 insertions(+), 3 deletions(-)
>
> diff --git a/cmds/subvolume-list.c b/cmds/subvolume-list.c
> index 382b0676..be7faca6 100644
> --- a/cmds/subvolume-list.c
> +++ b/cmds/subvolume-list.c
> @@ -35,7 +35,9 @@
> #include "common/open-utils.h"
> #include "common/string-utils.h"
> #include "common/utils.h"
> +#include "common/format-output.h"
> #include "cmds/commands.h"
> +#include "cmds/subvolume.h"
>
> /*
> * Naming of options:
> @@ -75,6 +77,8 @@ static const char * const cmd_subvolume_list_usage[] = {
> OPTLINE("--sort=gen,ogen,rootid,path", "list the subvolume in order of gen, ogen, rootid or path "
> "you also can add '+' or '-' in front of each items. "
> "(+:ascending, -:descending, ascending default)"),
> + HELPINFO_INSERT_GLOBALS,
> + HELPINFO_INSERT_FORMAT,
> NULL,
> };
>
> @@ -84,7 +88,8 @@ static const char * const cmd_subvolume_list_usage[] = {
> enum btrfs_list_layout {
> BTRFS_LIST_LAYOUT_DEFAULT = 0,
> BTRFS_LIST_LAYOUT_TABLE,
> - BTRFS_LIST_LAYOUT_RAW
> + BTRFS_LIST_LAYOUT_RAW,
> + BTRFS_LIST_LAYOUT_JSON
Json should not be a layout, that's relevant only for plain text output.
next prev parent reply other threads:[~2023-08-17 20:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 9:44 [PATCH 0/7] btrfs-progs: implement json output for subvolume subcommands Christoph Heiss
2023-08-13 9:44 ` [PATCH 1/7] btrfs-progs: common: document `time-long` output format Christoph Heiss
2023-08-13 9:44 ` [PATCH 2/7] btrfs-progs: subvol show: remove duplicated quotas error check Christoph Heiss
2023-08-13 9:44 ` [PATCH 3/7] btrfs-progs: subvol show: factor out text printing to own function Christoph Heiss
2023-08-13 9:44 ` [PATCH 4/7] btrfs-progs: subvol: introduce rowspec definition for json output Christoph Heiss
2023-08-13 9:45 ` [PATCH 5/7] btrfs-progs: subvol list: implement json format output Christoph Heiss
2023-08-17 19:59 ` David Sterba [this message]
2023-08-13 9:45 ` [PATCH 6/7] btrfs-progs: subvol get-default: " Christoph Heiss
2023-08-17 20:04 ` David Sterba
2023-08-18 18:49 ` Christoph Heiss
2023-08-13 9:45 ` [PATCH 7/7] btrfs-progs: subvol show: " Christoph Heiss
2023-08-17 20:02 ` David Sterba
2023-08-17 19:34 ` [PATCH 0/7] btrfs-progs: implement json output for subvolume subcommands David Sterba
2023-08-18 18:39 ` Christoph Heiss
2023-08-21 15:19 ` David Sterba
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=20230817195946.GV2420@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=christoph@c8h4.io \
--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