From: <zhong.shiqi@zte.com.cn>
To: <Markus.Elfring@web.de>
Cc: wang.yi59@zte.com.cn, michal.lkml@markovi.net,
nicolas.palix@imag.fr, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, xue.zhihong@zte.com.cn,
cheng.shengyu@zte.com.cn, cocci@systeme.lip6.fr
Subject: Re: [Cocci] [v4] coccicheck: Support search for SmPL scripts within selecteddirectory hierarchy
Date: Fri, 1 Nov 2019 10:49:16 +0800 (CST) [thread overview]
Message-ID: <201911011049160582771@zte.com.cn> (raw)
In-Reply-To: <d457995b-fed3-d560-e6b3-b8fa4b0059a0@web.de>
[-- Attachment #1.1: Type: text/plain, Size: 409 bytes --]
> I suggest to improve the case distinction for the make (and environment)
> variable “COCCI” also by adjusting the document outline.
> * Empty string
> * Directory selection
> * File name specification
>
> See also:
> https://docutils.readthedocs.io/en/sphinx-docs/user/rst/quickstart.html#sections
* Defalut value
* Directory selection
* Single file selection
Would it be better?
thanks,
Zhong.shiqi
[-- Attachment #2: Type: text/plain, Size: 136 bytes --]
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-11-01 2:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 7:50 [Cocci] [PATCH v4] coccicheck: Support search for SmPL scripts within selected directory hierarchy zhongshiqi
2019-10-26 14:12 ` Markus Elfring
2019-10-26 14:19 ` Markus Elfring
2019-10-30 2:59 ` [Cocci] [PATCH v4] coccicheck: Support search for SmPL scripts withinselected " zhong.shiqi
2019-10-30 8:40 ` [Cocci] [v4] coccicheck: Support search for SmPL scripts within selected " Markus Elfring
2019-11-01 2:49 ` zhong.shiqi [this message]
2019-11-01 8:20 ` Markus Elfring
2019-10-30 2:43 ` [Cocci] [PATCH v4] coccicheck: Support search for SmPL scripts withinselected " zhong.shiqi
2019-10-30 8:13 ` [Cocci] [v4] coccicheck: Support search for SmPL scripts within selected " 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=201911011049160582771@zte.com.cn \
--to=zhong.shiqi@zte.com.cn \
--cc=Markus.Elfring@web.de \
--cc=cheng.shengyu@zte.com.cn \
--cc=cocci@systeme.lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=wang.yi59@zte.com.cn \
--cc=xue.zhihong@zte.com.cn \
/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 NNTP newsgroup(s).