From: Daniel Wagner <wagi@monom.org>
To: Clark Williams <williams@redhat.com>
Cc: Daniel Wagner <dwagner@suse.de>, John Kacur <jkacur@redhat.com>,
linux-rt-users@vger.kernel.org
Subject: Re: [rt-tests 0/4] Streamlining code base?
Date: Fri, 4 Sep 2020 08:31:23 +0200 [thread overview]
Message-ID: <20200904063123.uu37gp4ipom64ao6@beryllium.lan> (raw)
In-Reply-To: <20200903203948.4d2e5370@tagon>
On Thu, Sep 03, 2020 at 08:39:48PM -0500, Clark Williams wrote:
> I think it's a noble goal and I'd be up for it, especially trying to come
> up with a parsable output format. Got any thoughts on it? Personally I'd
> go for (in order of preference):
>
> XML
> JSON
> Random Gibberish
> Any Damned thing
> YAML
For jitterdebugger I ended up adding a bunch of plugins for the output
format. So I don't have to argue which format it best, though if I had
to choose I'd properly pick JSON.
> Did I mention that I hate YAML?
Named must be your fear before banish it you can.
next prev parent reply other threads:[~2020-09-04 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 8:27 [rt-tests 0/4] Streamlining code base? Daniel Wagner
2020-09-02 8:27 ` [rt-tests 1/4] cyclicdeadline: Streamline usage output and man page Daniel Wagner
2020-09-02 8:27 ` [rt-tests 2/4] deadline_test: " Daniel Wagner
2020-09-02 8:27 ` [rt-tests 3/4] oslat: " Daniel Wagner
2020-09-02 8:27 ` [rt-tests 4/4] oslat: Use string parser utilies Daniel Wagner
2020-09-04 1:39 ` [rt-tests 0/4] Streamlining code base? Clark Williams
2020-09-04 6:31 ` Daniel Wagner [this message]
2020-09-04 15:40 ` John Kacur
2020-09-07 8:13 ` Daniel Wagner
2020-09-08 15:23 ` John Kacur
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=20200904063123.uu37gp4ipom64ao6@beryllium.lan \
--to=wagi@monom.org \
--cc=dwagner@suse.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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).