git/list[1] front-page[2] threads[3] people[4] search[5] about
 

coccinelle: fine-tuning for commit.cocci?

From
MEMarkus Elfring <markus.elfring@web.de>
Date
Nov 12, 2019, 17:50 UTC
Message-ID
<5ff15b03-aa04-f8f7-2989-cc5463e71d27@web.de>
Hello,

I would like to comment implementation details from the commit 301b8c7f405d3cd4f32b14bd336ac8c0400d9382 ("commit.c: add repo_get_commit_tree()").

1. Would you like to use a code variant (for the semantic patch language)
   which can work without a regular expression for the exclusion of a single item?
   identifier f != set_commit_tree;
2. How do you think about the following variants for the specification of SmPL constraints?
   * Advanced regular expression
     identifier f !~ "^(?:get_commit_tree_in_graph_one|load_tree_for_commit|(?:repo_g|s)et_commit_tree)$";
   * Item list filter
     identifier f != { get_commit_tree_in_graph_one, load_tree_for_commit, repo_get_commit_tree, set_commit_tree };

Regards, Markus

Message 1 of 1 in “coccinelle: fine-tuning for commit.cocci?”
  1. Markus ElfringNov 12, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.