From: Christoph Heiss <christoph@c8h4.io>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 1/7] btrfs-progs: common: document `time-long` output format
Date: Sun, 13 Aug 2023 11:44:56 +0200 [thread overview]
Message-ID: <20230813094555.106052-2-christoph@c8h4.io> (raw)
In-Reply-To: <20230813094555.106052-1-christoph@c8h4.io>
Seems this was forgotten; rectify that.
Signed-off-by: Christoph Heiss <christoph@c8h4.io>
---
common/format-output.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/common/format-output.h b/common/format-output.h
index 95e2a117..ab12a7f1 100644
--- a/common/format-output.h
+++ b/common/format-output.h
@@ -28,6 +28,8 @@ struct rowspec {
* (values: va_args)
* - uuid: format UUID as text
* (value: u8 *uuid)
+ * - time-long: pretty print timestamp, including timezone
+ * (values: time_t)
* - list: print list opening bracket [
* (values printed separately)
* - map: start a new group, opens {
--
2.41.0
next prev parent reply other threads:[~2023-08-13 9:51 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 ` Christoph Heiss [this message]
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
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=20230813094555.106052-2-christoph@c8h4.io \
--to=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