public inbox for cocci@systeme.lip6.fr
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>,
	Victor Gambier <victor.gambier@inria.fr>
Cc: cocci@inria.fr
Subject: Re: [cocci] Evolution for the software build system?
Date: Wed, 21 Jan 2026 17:21:42 +0100	[thread overview]
Message-ID: <421aee9d-5483-4c74-a149-778d439e33ff@web.de> (raw)
In-Reply-To: <258386cb-4f80-64a-4340-ec9b7c4d336@inria.fr>

>> Unfortunately, I would miss further improvements for the software build system so far.
>> https://gitlab.inria.fr/coccinelle/coccinelle/-/commit/b231de0db3f9513f6ea936caea5428fe627af1b9
>>
>> I tried also to influence corresponding adjustments somehow.
>> Will development interests grow accordingly?
> 
> If you want something to change, could you please explain what should
> change, or better yet provide a patch?

I pointed remaining update candidates out.

I presented some patches before.

I would appreciate if corresponding development discussions can become
more constructive again.


>                                         "miss further improvements" gives
> no information about what should be done.

Please take another look at previous clarification approaches.
Would you like to offer further answers to remaining open issues?

Regards,
Markus

  reply	other threads:[~2026-01-21 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 14:43 [cocci] Pre-compiled spatch links against EOL PCRE version Manuel Wiesinger
2025-12-16 14:35 ` Victor Gambier
2025-12-16 15:24   ` Markus Elfring
2026-01-21 11:14   ` Victor Gambier
2026-01-21 15:43     ` Markus Elfring
2026-01-21 15:57       ` Julia Lawall
2026-01-21 16:21         ` Markus Elfring [this message]
2026-01-21 16:23           ` [cocci] Evolution for the software build system? Julia Lawall
2026-01-21 16:55             ` Markus Elfring
2026-01-22  8:35             ` Markus Elfring
2026-02-02  7:01     ` [cocci] Improving software build systems? Markus Elfring

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=421aee9d-5483-4c74-a149-778d439e33ff@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@inria.fr \
    --cc=julia.lawall@inria.fr \
    --cc=victor.gambier@inria.fr \
    /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