public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Clark Williams <williams@redhat.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: John Kacur <jkacur@redhat.com>, linux-rt-users@vger.kernel.org
Subject: Re: [rt-tests 0/4] Streamlining code base?
Date: Thu, 3 Sep 2020 20:39:48 -0500	[thread overview]
Message-ID: <20200903203948.4d2e5370@tagon> (raw)
In-Reply-To: <20200902082725.20037-1-dwagner@suse.de>

On Wed,  2 Sep 2020 10:27:21 +0200
Daniel Wagner <dwagner@suse.de> wrote:

> Hi Clark and John,
> 
> I'd like to streamline all tools, so that the usage, command arguments
> and the output is more consistent. Every tool seems to be a bit
> different which makes all automatization around the tools more complex
> than needed.
> 
> Eventually, I'd like to add an easy machine parseable output from all
> tools. So what do you think? Stupid effort, go away?

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

Clark

Did I mention that I hate YAML?

> 
> Here are a bunch of patches to illustrate what I mean. Before invest
> too much time I'd like to discuss it, e.g. format.
> 
> Cheers,
> Daniel
> 
> Daniel Wagner (4):
>   cyclicdeadline: Streamline usage output and man page
>   deadline_test: Streamline usage output and man page
>   oslat: Streamline usage output and man page
>   oslat: Use string parser utilies
> 
>  src/include/rt-utils.h              |   1 +
>  src/lib/rt-utils.c                  |  30 ++++++
>  src/oslat/oslat.8                   |   2 +-
>  src/oslat/oslat.c                   | 143 ++++++++--------------------
>  src/sched_deadline/cyclicdeadline.8 |  24 ++---
>  src/sched_deadline/cyclicdeadline.c |  41 ++++----
>  src/sched_deadline/deadline_test.8  |  37 ++++---
>  src/sched_deadline/deadline_test.c  |  47 +++++----
>  8 files changed, 145 insertions(+), 180 deletions(-)
> 
> -- 
> 2.28.0
> 


-- 
The United States Coast Guard
Ruining Natural Selection since 1790


  parent reply	other threads:[~2020-09-04  1:39 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 ` Clark Williams [this message]
2020-09-04  6:31   ` [rt-tests 0/4] Streamlining code base? Daniel Wagner
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=20200903203948.4d2e5370@tagon \
    --to=williams@redhat.com \
    --cc=dwagner@suse.de \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@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