All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] 1.0.0-rc23 release - Clarification of build tweaks
Date: Sat, 13 Dec 2014 12:18:11 +0100	[thread overview]
Message-ID: <548C2073.7080209@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1412131202520.2062@localhost6.localdomain6>

>> Who did update the build files like "configure.ac" and "commons/Makefile"?
>> https://github.com/coccinelle/coccinelle/commit/c5ff9aff461df30b31ff23b17d2487127c8b9d0a#diff-67e997bcfdac55191033d57a16d1408a
> Why do you want to know this?

We have got a few difficulties in the past to find someone for further
consideration of my proposed corrections around the affected build scripts.
Did the expertise concerns change a bit in the meantime?


> They were updated mostly to accomodate changes in more recent versions of ocaml.

I find that it would also be nice to mention such adjustments in the
release notes, wouldn't it?

Regards,
Markus

  parent reply	other threads:[~2014-12-13 11:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 13:16 [Cocci] 1.0.0-rc23 release Julia Lawall
2014-12-11 14:57 ` SF Markus Elfring
     [not found]   ` <alpine.DEB.2.10.1412131601220.2114@hadrien>
2014-12-15 18:35     ` [Cocci] 1.0.0-rc23 release - Download links SF Markus Elfring
2014-12-13 10:38 ` [Cocci] 1.0.0-rc23 release - Clarification of build tweaks SF Markus Elfring
     [not found]   ` <alpine.DEB.2.02.1412131202520.2062@localhost6.localdomain6>
2014-12-13 11:18     ` SF Markus Elfring [this message]
2014-12-16 10:55     ` SF Markus Elfring
2014-12-16 14:53       ` Julia Lawall
2014-12-16 19:50         ` SF Markus Elfring
2014-12-16 11:17 ` [Cocci] 1.0.0-rc23 release - Menhir updates SF Markus Elfring
2014-12-16 14:51   ` Julia Lawall
2014-12-16 20:00     ` 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=548C2073.7080209@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --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.