From: rjones@redhat.com (Richard W.M. Jones)
To: cocci@systeme.lip6.fr
Subject: [Cocci] 1.0.0-rc16: Further fine-tuning for the build system?
Date: Fri, 26 Apr 2013 09:14:34 +0100 [thread overview]
Message-ID: <20130426081434.GA3645@redhat.com> (raw)
In-Reply-To: <5144D0F8.3040302@users.sourceforge.net>
On Sat, Mar 16, 2013 at 09:07:20PM +0100, SF Markus Elfring wrote:
> > I have got the impression that there are more update candidates to consider
> > since the macro call "AM_INIT_AUTOMAKE" was added.
>
> Are you going to update and complete any components from your build
> specification and corresponding configuration scripts?
[Since you asked me in private email to contribute to
this discussion ...]
I think you're being unreasonable asking the Coccinelle developers to
fix things, and hardly specifying what the problem is (from what I can
gather it's something to do with separated builds not working?).
In any case, supply patches, with clear explanations behind each one.
So far I see one patch, probably incomplete, and no clear explanation
for it.
http://people.redhat.com/rjones/how-to-supply-code-to-open-source-projects/
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
next prev parent reply other threads:[~2013-04-26 8:14 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 ` Richard W.M. Jones [this message]
2013-04-26 9:10 ` [Cocci] 1.0.0-rc16: " 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
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=20130426081434.GA3645@redhat.com \
--to=rjones@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.