archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <>
To: Denis Efremov <>, Coccinelle <>
Cc: Gilles Muller <>,
	Julia Lawall <>,
	Masahiro Yamada <>,
	Michal Marek <>,
	Nicolas Palix <>,,,
	"Gustavo A. R. Silva" <>,
	Kees Cook <>
Subject: Re: Coccinelle: Improving convenience for message exchange
Date: Fri, 19 Jun 2020 11:15:43 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> I can't handle your suggestions

I hope that you can work with provided information to some degree.

> because your mails constantly break the threads.

Would you like to take another look at reasons for such an effect?

> I just can't find them

Please try again.
Were relevant data stored in usable message folders?

> after due to missed/wrong In-Reply-To headers.

How do you think about to influence the situation in ways
which can improve the desired data processing considerably?


      parent reply	other threads:[~2020-06-19 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 11:34 [PATCH v2] coccinelle: misc: add array_size_dup script to detect missed overflow checks Markus Elfring
2020-06-18 12:24 ` Denis Efremov
2020-06-18 15:01   ` Markus Elfring
2020-06-18 15:01   ` Markus Elfring
2020-06-19 11:15   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).