From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Documentation check for parallelisation support?
Date: Mon, 18 Jan 2016 21:25:22 +0100 [thread overview]
Message-ID: <569D4A32.6030909@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1601181138430.2520@hadrien>
>> Will this aspect need further considerations because of the evolving
>> parallelisation support?
>> https://github.com/coccinelle/coccinelle/issues/50
>
> I believe that parallelism with -j only fails if there is a finalize.
> An initialize by itself should be OK.
Does the corresponding wording need another update in the SmPL manual?
https://github.com/coccinelle/coccinelle/blob/246fb87e74e448b46749601a25fa019925b07e43/docs/manual/spatch_options.tex#L678
Regards,
Markus
prev parent reply other threads:[~2016-01-18 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 8:47 [Cocci] script code on metavariables Julia Lawall
2016-01-18 10:11 ` SF Markus Elfring
2016-01-18 10:15 ` Julia Lawall
2016-01-18 10:30 ` SF Markus Elfring
2016-01-18 10:43 ` Julia Lawall
2016-01-18 12:00 ` SF Markus Elfring
2016-01-18 12:05 ` Julia Lawall
2016-01-18 12:28 ` SF Markus Elfring
2016-01-18 20:25 ` SF Markus Elfring [this message]
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=569D4A32.6030909@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox