[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37ad0bcd-941d-e02e-ae99-e89f2ce98ff0@web.de>
Date: Thu, 24 Oct 2019 09:55:34 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Julia Lawall <julia.lawall@...6.fr>, cocci@...teme.lip6.fr
Cc: linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
Cheng Shengyu <cheng.shengyu@....com.cn>,
Gilles Muller <Gilles.Muller@...6.fr>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Michal Marek <michal.lkml@...kovi.net>,
Nicolas Palix <nicolas.palix@...g.fr>,
Yi Wang <wang.yi59@....com.cn>,
Xue Zhihong <xue.zhihong@....com.cn>,
Zhong Shiqi <zhong.shiqi@....com.cn>
Subject: Re: [PATCH v2] coccicheck: support $COCCI being defined as a
directory
> Second the commit log could be more concise as:
I like your desire for choosing a more appropriate commit message.
> Allow defining COCCI as a directory that contains .cocci files.
I would prefer to concentrate the patch subject on other information.
> In general, at least in simple cases, it is not necessary to mention the
> name of the file you are modifying in the comit log, because one can see
> that just below from looking at the diffstat and the patch.
This view can be reasonable. - How does it fit to the usual requirement
for the specification of a “subsystem” (or “prefix”) according to the
canonical patch format?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=13b86bc4cd648eae69fdcf3d04b2750c76350053#n656
Regards,
Markus
Powered by blists - more mailing lists