mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Knut Omang <knut.omang@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [v3] runchecks: Generalize make C={1, 2} to support multiple checkers
Date: Fri, 5 Jan 2018 15:45:06 +0100	[thread overview]
Message-ID: <3eced649-7dd2-b353-9e71-3926df844f1d@users.sourceforge.net> (raw)
In-Reply-To: <1515096931.31439.647.camel@oracle.com>

> I do feel confident that the benefits of python for this outweighs the drawbacks
> compared to my initial shell script implementation, or using perl or even C.
>
> Further advice on this appreciated,

I got further ideas around this software situation. I am curious on how they fit
to your vision.

One of the challenges for integration of your contribution can also be the
acceptance of corresponding configuration files. There are design choices
available to work with suggested data structures.

How do you think about the develop an official data format specification
for which the shown Python script could be the first reference implementation?
Alternative implementations could be applied on concrete demand.


I would like to add another development concern:

* Do all (Python) classes need to be stored within the same script file so far?

* Do we need to think about structures around plug-ins (or add-ons) already?

Regards,
Markus

  parent reply	other threads:[~2018-01-05 14:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 13:39 [PATCH v3 0/1] Support for generalized use of make C={1,2} via a wrapper program Knut Omang
2018-01-04 13:39 ` [PATCH v3 1/1] runchecks: Generalize make C={1,2} to support multiple checkers Knut Omang
2018-01-04 15:50   ` Jani Nikula
2018-01-04 20:15     ` Knut Omang
2018-01-05 14:30       ` Jani Nikula
2018-01-05 16:05         ` Markus Heiser
2018-01-07 12:03         ` Philippe Ombredanne
2018-01-07 13:13           ` Knut Omang
2018-01-05 14:45       ` SF Markus Elfring [this message]
2018-01-05 18:08       ` Mauro Carvalho Chehab
2018-01-05 19:41         ` Knut Omang
2018-01-07 10:12           ` Mauro Carvalho Chehab
2018-01-08  7:33             ` Knut Omang

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=3eced649-7dd2-b353-9e71-3926df844f1d@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=cocci@systeme.lip6.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=knut.omang@oracle.com \
    --cc=linux-kernel@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

Powered by JetHome