From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] 1.0.0-rc16: Further fine-tuning for the build system?
Date: Fri, 26 Apr 2013 18:25:02 +0800 (SGT) [thread overview]
Message-ID: <alpine.DEB.2.02.1304261816530.1985@hadrien> (raw)
In-Reply-To: <517A53C5.4030902@users.sourceforge.net>
On Fri, 26 Apr 2013, SF Markus Elfring wrote:
>
> > It's NOT by badgering Coccinelle upstream
>
> If Julia will show more willingness to handle patches for the build system, I
> am going also to invest more efforts into concrete fixes.
>
>
> > and trying to get other people to argue your case for you.
>
> I do not want that, too. But other software developers might have got a higher
> reputation so that their update suggestions or source code review advices get
> easier accepted than change requests from me.
My point of view regarding the build system is that, on the one hand, at
the moment, I don't have any local resources with expertise in build
systems and on the other hand the build setup is extremely critical.
So I am not currently willing to make changes without an actual need from
a user. An actual need would be a case where it is impossible to build
Coccinelle in any way on a given machine. It is not a case where eg out
of tree builds don't work or parallel builds don't work. In those cases,
one can easily avoid the problem by building in another way.
If several people want to work on and validate any solution that adds some
such inessential functionality, then I might consider integrating the
change. But I don't have the expertise to evaluate such patches myself,
so I won't integrate such patches if they have only been tested by the
submitter.
This doesn't apply to ML patches. I have received several patches adding
support for various strange C extensions, and I have no problem with
integrating them. The risk is lower and the potential benefit is higher.
julia
next prev parent reply other threads:[~2013-04-26 10:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 21:02 [Cocci] 1.0.0-rc16: Further fine-tuning for the build system? SF Markus Elfring
2013-03-02 21:18 ` Julia Lawall
2013-03-04 11:35 ` SF Markus Elfring
2013-03-04 12:36 ` Julia Lawall
2013-03-04 12:37 ` Julia Lawall
2013-03-04 12:43 ` SF Markus Elfring
2013-03-04 12:48 ` Julia Lawall
2013-03-04 13:14 ` SF Markus Elfring
2013-03-04 13:54 ` SF Markus Elfring
2013-03-04 15:40 ` SF Markus Elfring
2013-03-04 15:47 ` Julia Lawall
2013-03-04 16:05 ` SF Markus Elfring
2013-03-05 8:36 ` Arie Middelkoop
2013-03-07 15:54 ` SF Markus Elfring
2013-03-07 16:27 ` Arie Middelkoop
2013-03-07 17:07 ` SF Markus Elfring
2013-03-16 20:07 ` SF Markus Elfring
2013-03-17 12:18 ` Arie Middelkoop
2013-03-18 9:50 ` SF Markus Elfring
2013-04-07 10:51 ` [Cocci] 1.0.0-rc17: " SF Markus Elfring
2013-04-07 11:05 ` Julia Lawall
2013-04-07 11:14 ` SF Markus Elfring
2013-04-07 11:20 ` Julia Lawall
2013-04-07 11:30 ` SF Markus Elfring
2013-04-07 11:43 ` Julia Lawall
2013-04-07 12:07 ` SF Markus Elfring
2013-04-07 12:11 ` Julia Lawall
2013-04-07 12:13 ` SF Markus Elfring
2013-04-26 8:14 ` [Cocci] 1.0.0-rc16: " Richard W.M. Jones
2013-04-26 9:10 ` SF Markus Elfring
2013-04-26 9:16 ` Richard W.M. Jones
2013-04-26 9:36 ` SF Markus Elfring
2013-04-26 9:52 ` Richard W.M. Jones
2013-04-26 10:15 ` SF Markus Elfring
2013-04-26 10:25 ` Julia Lawall [this message]
2013-04-26 11:03 ` Peter Senna Tschudin
2013-04-26 11:28 ` SF Markus Elfring
2013-04-29 9:52 ` [Cocci] 1.0.0-rc17: " SF 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=alpine.DEB.2.02.1304261816530.1985@hadrien \
--to=julia.lawall@lip6.fr \
--cc=cocci@systeme.lip6.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