public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH] newlib: Allow sub-tests to be specified in a list
Date: Wed, 04 Oct 2017 10:04:37 +0200	[thread overview]
Message-ID: <8760bvwd7u.fsf@our.domain.is.not.set> (raw)
In-Reply-To: <20171003144157.GD11692@rei>

Hello,

Cyril Hrubis writes:

> Hi!
> That is even more complicated than my patch with array:
>
> http://lists.linux.it/pipermail/ltp/2017-July/005132.html
>
> And Jan didn't even liked mine because it adds complexity complexity
> that is uncalled for...

I think it is called for (atleast the idea in general is) because it
encourages people to write similar tests in a clean way which should
save time in the long run.

I am hoping someone comes up with an acceptable way of doing it.

--
Thank you,
Richard.

      reply	other threads:[~2017-10-04  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 13:55 [LTP] [RFC PATCH] newlib: Allow sub-tests to be specified in a list Richard Palethorpe
2017-10-03 14:41 ` Cyril Hrubis
2017-10-04  8:04   ` Richard Palethorpe [this message]

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=8760bvwd7u.fsf@our.domain.is.not.set \
    --to=rpalethorpe@suse.de \
    --cc=ltp@lists.linux.it \
    /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