From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>, cocci@systeme.lip6.fr
Cc: Yi Wang <wang.yi59@zte.com.cn>,
Michal Marek <michal.lkml@markovi.net>,
Nicolas Palix <nicolas.palix@imag.fr>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Xue Zhihong <xue.zhihong@zte.com.cn>,
Cheng Shengyu <cheng.shengyu@zte.com.cn>,
Zhong Shiqi <zhong.shiqi@zte.com.cn>
Subject: Re: [Cocci] [v2] coccicheck: support $COCCI being defined as a directory
Date: Thu, 24 Oct 2019 11:11:49 +0200 [thread overview]
Message-ID: <9807ba7a-5ab7-10ac-5e6e-5279b51c423b@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1910240956450.4479@hadrien>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=13b86bc4cd648eae69fdcf3d04b2750c76350053#n656
>
> Huh? I was talking about the log message, not the subject line.
Thanks for this clarification.
> With that degree of orientation, I think one can look at the code
> and figure out what the intent is.
The intention should become clear by reading the commit message
(combination of a subject and change description) alone already,
shouldn't it?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-10-24 9:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 6:04 [Cocci] [PATCH v2] coccicheck:support $COCCI being defined as a directory zhongshiqi
2019-10-24 6:19 ` Julia Lawall
2019-10-24 7:55 ` [Cocci] [PATCH v2] coccicheck: support " Markus Elfring
2019-10-24 7:58 ` Julia Lawall
2019-10-24 9:11 ` Markus Elfring [this message]
2019-10-24 8:02 ` [Cocci] [PATCH v2] coccicheck:support $COCCI being defined as adirectory zhong.shiqi
2019-10-24 7:06 ` [Cocci] [PATCH v2] coccicheck: support $COCCI being defined as a directory Markus Elfring
2019-10-24 8:03 ` [Cocci] [PATCH v2] coccicheck: support $COCCI being defined as adirectory zhong.shiqi
2019-10-24 9:23 ` [Cocci] [v2] " Markus Elfring
2019-10-24 9:58 ` zhong.shiqi
2019-10-24 10:52 ` [Cocci] [v2] coccicheck: support $COCCI being defined as a directory 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=9807ba7a-5ab7-10ac-5e6e-5279b51c423b@web.de \
--to=markus.elfring@web.de \
--cc=cheng.shengyu@zte.com.cn \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@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 \
--cc=zhong.shiqi@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).