From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev <dev@dpdk.org>, "Morten Brørup" <mb@smartsharesystems.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Ciara Power" <ciara.power@intel.com>
Subject: Re: [PATCH] doc: add deprecation for restrictions in telemetry naming
Date: Mon, 11 Jul 2022 12:45:19 +0200 [thread overview]
Message-ID: <CAJFAV8w2dqMCAGe08u8jPB3s+j7AiV_7xnLLB9PRcxg6r0ov5Q@mail.gmail.com> (raw)
In-Reply-To: <20220707133931.752248-1-bruce.richardson@intel.com>
On Thu, Jul 7, 2022 at 3:39 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> Following discussion on-list [1], we will look to limited the allowed
> characters in names for items in telemetry. This will simplify the
> escaping needed for json output, or any future output formats. The lists
> will initially be minimal, since expansion to allow more characters can
> be done without affecting compatibility, while reducing the set cannot.
>
> Cc: mb@smartsharesystems.com
> Cc: stephen@networkplumber.org
> Cc: ciara.power@intel.com
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
next prev parent reply other threads:[~2022-07-11 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 13:39 Bruce Richardson
2022-07-07 15:16 ` Andrew Rybchenko
2022-07-07 22:06 ` Morten Brørup
2022-07-11 10:53 ` Bruce Richardson
2022-07-11 11:40 ` Morten Brørup
2022-07-11 10:43 ` Power, Ciara
2022-07-11 10:45 ` David Marchand [this message]
2022-07-12 9:04 ` [PATCH v2] " Bruce Richardson
2022-07-12 9:09 ` [PATCH v3] " Bruce Richardson
2022-07-15 16:30 ` Thomas Monjalon
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=CAJFAV8w2dqMCAGe08u8jPB3s+j7AiV_7xnLLB9PRcxg6r0ov5Q@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=stephen@networkplumber.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).