From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: [cocci] Marking several issues as “not planned”
Date: Tue, 19 Nov 2024 14:14:27 +0100 [thread overview]
Message-ID: <e3af9f65-c923-4fa0-8a7d-be1b27d47fb5@web.de> (raw)
Hello,
Various issues were marked as “not planned” recently.
https://github.com/coccinelle/coccinelle/issues?q=is%3Aissue+reason%3A%22not+planned%22
Does such an action trigger questionable impressions?
Regards,
Markus
next reply other threads:[~2024-11-19 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 13:14 Markus Elfring [this message]
2024-11-19 14:34 ` [cocci] Marking several issues as “not planned” Victor Gambier
2024-11-19 15:20 ` Markus Elfring
2024-11-19 15:22 ` Victor Gambier
2024-11-19 15:32 ` Markus Elfring
2024-11-19 15:34 ` Derek M Jones
2024-11-19 15:38 ` Victor Gambier
2024-11-20 8:46 ` [cocci] Marking several issues as … 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=e3af9f65-c923-4fa0-8a7d-be1b27d47fb5@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).